Bug 48705 - flag to allow newlines in the error log as opposed to a compile time directive
Summary: flag to allow newlines in the error log as opposed to a compile time directive
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.11
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-02-08 12:01 UTC by brian j
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brian j 2010-02-08 12:01:48 UTC
apache 1+ allowed newlines to be printed in the error log.
apache 2+ now needs a compile time directive to enable this...

This should be a .conf file modifiable parameter as opposed to a compile time directive.  The user should have easy control over this VERY useful debugging option as opposed to having to download the source and recompile.

Recompiling isn't an option at a lot of places they require all packages to come from a repository or for developers that need to maintain the same levels of the application in their sandboxes, test, QA, and production environments.

This option should be enabled by default with the override parameter in the .conf file set to not allow unescaped characters in the error log.

CFLAGS=-DAP_UNSAFE_ERROR_LOG_UNESCAPED
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:33 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.