Start/notes.ini Parameters/DEBUG_HTTP_RESPONSE

DEBUG_HTTP_RESPONSE

🛠️
Parameter: DEBUG_HTTP_RESPONSE
Short description: Logs HTTP response headers and status codes returned by the Domino HTTP stack – counterpart to DEBUG_HTTPINOUT, but focused on the response side.

Profile

Parameter
DEBUG_HTTP_RESPONSE
Category
Logging / Debug
Component
Server
Available since
10.0
Supported versions
10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
0 = off (default), 1 = headers, 2 = headers + body size

Description

While DEBUG_HTTPINOUT records request and response data together, DEBUG_HTTP_RESPONSE focuses exclusively on the response side. For each HTTP request, the server writes the status code, response headers, and (at level 2) the size of the response body to the log.
Helps with topics such as browser receives 500 instead of 200 – what's in the header?, cache headers are not set, cookies/session headers are missing, redirects lead nowhere. Together with the access log (domlog.nsf / xxxx.nlog), this gives a complete picture of HTTP responses.

Example configuration

DEBUG_HTTP_RESPONSE=1
Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/http_response_debug.log

Notes & pitfalls

  • Level 2 produces a lot of output on active servers.
  • Takes effect immediately via set config DEBUG_HTTP_RESPONSE=1; a restart of the HTTP task is not strictly required.
  • Entries appear in console.log and in Debug_Outfile.
  • Complementary to DEBUG_HTTPINOUT, Debug_Outfile, domlog.nsf.
  • Sensitive headers (auth, cookies) may be logged – consider log retention.