[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-10-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #28 from Rainer Jung --- Why do you think your observation has any realtion to this bug here. The original bug is about directory listings and you problem seems to be HEAD against an existing file system object. Please post your

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-10-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 Jean Weisbuch changed: What|Removed |Added OS|Mac OS X 10.1 |Linux --- Comment #27 from Jean

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 Luca Toscano changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #25 from Luca Toscano --- (In reply to Yann Ylavic from comment #24) > Committed to trunk in r1837130. Thanks a lot for the fix Yann! In @dev Cory proposed another solution (mod_ratelimit only), can we also follow up in there to

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 Yann Ylavic changed: What|Removed |Added Keywords||FixedInTrunk --- Comment #24 from Yann

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #23 from Yann Ylavic --- OK, thanks for the clarification and tests. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe,

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #22 from snakedo...@gmail.com --- *doh* I was just copying the sbin/httpd binary over, and not doing a full install (so that I could easily switch back to the non-patched version). Obviously, that missed mod_ratelimit.so. Once I

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #21 from Yann Ylavic --- And, by the way, did you ./configure with --enable-ratelimit=shared ? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #20 from Yann Ylavic --- It seems that the original/old version is running, not the patched one. By looking at the modification date of "mod_ratelimit.so" in your runtime tree, does it match the one of the build tree? -- You are

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #19 from snakedo...@gmail.com --- That's weird. I know mod_ratelimit is working, because when I load the directory with a configuration of "SetEnv rate-limit 4", it loads the raw HTML _extremely slow_ (as expected, at least with

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #18 from Yann Ylavic --- There is no log message from mod_ratelimit, so somehow "mod_ratelimit.so" used at runtime isn't a patched one. Something went wrong in your patching/install procedure... -- You are receiving this mail

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #17 from snakedo...@gmail.com --- Created attachment 36059 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36059=edit log1.txt Here is the log with mod_dumpio enabled. 22:30:xx = without rate limiting enabled. 22:31:xx =

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 Yann Ylavic changed: What|Removed |Added Attachment #36055|0 |1 is obsolete|

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #15 from snakedo...@gmail.com --- Here's my log with trace7. The 12:56:xx time frame was /tmp directory with 0 files in it (success). The 12:57:xx time frame was /tmp directory with 61 files in it (failure). [Mon Jul 30

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 Yann Ylavic changed: What|Removed |Added Attachment #36049|0 |1 is obsolete|

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #13 from Yann Ylavic --- I can't reproduce either with the patch applied. snakedoctr, could you please provide the error_log with LogLevel trace7? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #12 from Luca Toscano --- Ah ok now I realized one thing, namely that in my dir listing tests I don't get a chunked response (don't see the Transfer-Encoding: chunked response header). Need to re-test it again and see if I can

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #11 from snakedo...@gmail.com --- Removed the patch, and same result -- headers in output using curl. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #10 from Luca Toscano --- Ok good, this is exactly the problem that should be solved with the patch, let's concentrate on it. If you try without the patch, what do you get? In theory the same result, but a confirmation would be

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #9 from snakedo...@gmail.com --- Curl is definitely showing the headers in the output. e.g. 2029 HTTP/1.1 200 OK Date: Fri, 27 Jul 2018 15:02:16 GMT Server: Apache Transfer-Encoding: chunked Content-Type:

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #8 from Luca Toscano --- Can you try with curl or even telnet to see what the server returns? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #7 from snakedo...@gmail.com --- That's weird. I'm certain the patch is applied. I'm using the FreeBSD ports version of 2.4.34, which does have some patches, but the patch is applying cleanly, so it should be fine. What's weird

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #6 from Luca Toscano --- Thanks a lot for testing! In theory the patch should avoid the use case that you mentioned for last, and in my testing environment the repro case that you described works fine (directory listing with 62

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #5 from snakedo...@gmail.com --- I applied the patch, and instead of the browser throwing an error like it did before the patch, it now dumps the raw HTML with headers at the top. e.g., 2061 HTTP/1.1 200 OK Date: Thu, 26 Jul 2018

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #4 from Luca Toscano --- Created attachment 36049 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36049=edit rate_limit_filter+header_only.patch -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #3 from Luca Toscano --- Hi! Apologies for the regression, sadly we (most of the blame on me though!) failed to check chunked responses while testing. While trying to fix mod_ratelimit with proxied content we introduced a new

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #2 from Eric Covener --- This regression is being worked here: https://www.mail-archive.com/dev@httpd.apache.org/msg71614.html -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62568] ERR_INVALID_HTTP_RESPONSE as of 2.4.34 when listing directories

2018-07-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62568 --- Comment #1 from snakedo...@gmail.com --- I should have also said this is when using mod_dir (directory indexes). -- You are receiving this mail because: You are the assignee for the bug.