Start/notes.ini Parameters/HTTPEnablePostDataLogging

HTTPEnablePostDataLogging

Parameter: HTTPEnablePostDataLogging
Short description: Extends the HTTP request logging with the data received in the POST body. Takes effect in addition to HTTPEnableThreadDebug. Only for troubleshooting.

Profile

Parameter
HTTPEnablePostDataLogging
Component
Server (HTTP task)
Category
Logging / Debug
Available since
9.0.x (per KB0032210)
Default
0 (disabled)
Values
0 off, 1 on
Works with
HTTPEnableThreadDebug=1
Console
tell http debug postdata on \| off
Storage location
htthr_*.log in IBM_TECHNICAL_SUPPORT

Description

The standard thread logging of the Domino HTTP task (HTTPEnableThreadDebug=1) records the request headers and response headers per HTTP request. The actual request bodies — i.e. the contents of POST requests, such as form data or JSON payloads — are not written.
With HTTPEnablePostDataLogging=1, the incoming POST bodies are additionally recorded in the htthr_*.log files. This is helpful when analyzing problems that only occur with certain input data (validation errors, encoding, cross-site/injection suspicion, servlet bugs, faulty form submissions).

Activation

Statically via notes.ini (takes effect at the next HTTP start):
HTTPEnableThreadDebug=1
HTTPEnablePostDataLogging=1
Dynamically via the server console, without restart:
tell http debug thread on
tell http debug postdata on
Deactivate with:
tell http debug postdata off

Important notes

  • Sensitive data – POST bodies often contain passwords, API keys, session tokens, personal data, or other confidential information. Only enable the logging for targeted reproduction and delete the logs after analysis.
  • Disk space – since bodies can become arbitrarily large (e.g. file uploads), the log file grows very quickly. HCL explicitly warns in KB0032210 against leaving the logging permanently active.
  • Dependency – the parameter only takes meaningful effect in combination with HTTPEnableThreadDebug=1, since the thread log is what creates the file in the first place.
  • Counterpart for responses – to also log the server response body, additionally enable HTTPEnableResponseContentLogging=1. This grows the logs significantly again.
  • Use after troubleshooting – HCL explicitly recommends using HTTP request logging only under support guidance and disabling it again after analysis.

Sources (HCL Product Documentation)