Parameter:
HTTPDebugLogOnlyLastRequestShort description: Writes only the most recent HTTP request to the HTTP debug log – useful for reproducing specific errors.
Profile
Parameter | HTTPDebugLogOnlyLastRequest |
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 = as before (accumulating log), 1 = keep only the last request |
Description
On production servers, the HTTP debug log can grow huge within seconds. When reproducing a specific error scenario, it is usually enough to evaluate only the most recently executed request in detail.
HTTPDebugLogOnlyLastRequest=1 instructs the HTTP task to overwrite the debug log after each request (instead of appending). After a reproduction, this leaves precisely the "golden" request that triggered the error – without having to wade through gigabytes of preceding traffic.Example configuration
HTTPDebugLogOnlyLastRequest=1
Notes & pitfalls
- Only useful with active debug mode (
HTTPDebugLogLevel/HTTPLogAccessOptionset accordingly).
- On multi-user servers, the log overwrites itself constantly – a reproducible single-user test is recommended.
- Takes effect immediately, no restart required.
- After the analysis, disable debug logging again to avoid performance loss.