[Bug 58231] RewriteCond can add "Host" to the Vary-Header

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58231 Luca Toscano changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 58231] RewriteCond can add "Host" to the Vary-Header

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58231 --- Comment #24 from Luca Toscano --- Backport committed in r1815100. I don't see more actionable for this task, closing it, thanks everybody for the help! And please re-open if I am missing something :) -- You are

[Bug 61818] New: OCSP "SSLUseStapling on" completely blocking the server when something is off with the responder

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61818 Bug ID: 61818 Summary: OCSP "SSLUseStapling on" completely blocking the server when something is off with the responder Product: Apache httpd-2 Version: 2.4.29 Hardware:

[Bug 61485] Segfault in log_io

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61485 --- Comment #9 from Luca Toscano --- Hi there, any chance that you got a core-dump? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61818] OCSP "SSLUseStapling on" completely blocking the server when something is off with the responder

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61818 --- Comment #1 from Christophe JAILLET --- This is odd. All paths that lead to this error (AH01941) seem to have some additional information logged at APLOG_ERR level. -- You are receiving this mail because:

[Bug 61820] New: 304 headers stripped

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61820 Bug ID: 61820 Summary: 304 headers stripped Product: Apache httpd-2 Version: 2.0-HEAD Hardware: All OS: All Status: NEW Severity: normal

[Bug 61818] OCSP "SSLUseStapling on" completely blocking the server when something is off with the responder

2017-11-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61818 --- Comment #2 from Raffaele Sandrini --- I just rescanned the log files, vhost specific and server log file, and I could not find any other related messages than the ones mentioned above (AH01941, AH00484 and