[Bug 1668474]

2022-03-08 Thread Ylavic-dev
Backported to 2.4.x (r1898588), will be in 2.4.53. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668474 Title: AH00526 when using long ProxyPass worker name To manage notifications about this bug

[Bug 1668474]

2021-12-22 Thread Ylavic-dev
I created https://github.com/apache/httpd/pull/288, would you try the patch there (https://patch- diff.githubusercontent.com/raw/apache/httpd/pull/288.diff)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1641238]

2020-03-29 Thread Ylavic-dev
(In reply to Lubos Uhliarik from comment #50) This follow up issue is being handled in bug 63891, a patch for 2.4 is available there (not yet backported to 2.4.next). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launch

[Bug 1641238]

2019-05-28 Thread Ylavic-dev
Yes, likely scheduled for 2.4.40, missing one vote only. Please note that the patch has been updated to v6 to resolve some conflicts from unrelated changes already merged in 2.4.40. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. http

[Bug 1641238]

2019-04-03 Thread Ylavic-dev
Yes, the patch did not make it to 2.4.39 which was mainly a security release, and this change is not really trivial.. Hopefully 2.4.40 is coming soon. As for v5 ([0] below, just in case), I just tried to apply it on top of 2.4.39 (from svn) and then to apply the freebsd patches from your link, but

[Bug 1641238]

2019-03-13 Thread Ylavic-dev
Everything looks fine until: [Fri Mar 08 15:23:06.165463 2019] [proxy:error] [pid 869:tid 140678264567552] (104)Connection reset by peer: [client 127.0.0.1:53920] AH01084: pass request body failed to 127.0.0.1:42180 (localhost) [Fri Mar 08 15:23:06.165530 2019] [proxy_http:error] [pid 869:tid 14

[Bug 1641238]

2019-03-08 Thread Ylavic-dev
Looks like a backend error, could you please provide the error log with LogLevel trace7 and mod_dumpio configured (DumpIoInput on, DumpIoOutput on)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/164123

[Bug 1641238]

2019-03-08 Thread Ylavic-dev
The latest patch is: http://people.apache.org/~ylavic/patches/httpd-2.4.x-forward_100_continue-v4.patch What's the problem in your case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title:

[Bug 1641238]

2019-02-19 Thread Ylavic-dev
Thanks Michael for the very appropriate test: first 401 which avoids the "100 continue" danse and thus gets forwarded with "connection: close", second 201 with the full thing. Great! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. htt

[Bug 1641238]

2019-02-12 Thread Ylavic-dev
(In reply to Yann Ylavic from comment #28) > tomcat CONNECTORS-1564 Looks like it's Solr actually, but all tests are welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title: as a rever

[Bug 1641238]

2019-02-12 Thread Ylavic-dev
Proposed for backport to 2.4.x (r1853409), let's see what other committers think, notably if it's too much of a change for the stable branch. If so, this will have to wait for next 2.6/3.0... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 1641238]

2019-02-12 Thread Ylavic-dev
Also, testing the tomcat CONNECTORS-1564 case with the final patch ([1]) would be very welcome ;) [1] http://people.apache.org/~ylavic/patches/httpd-2.4.x-forward_100_continue.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. http

[Bug 1641238]

2018-07-25 Thread Ylavic-dev
Thanks for testing Michael. Fixed in r1836648 (hopefully). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title: as a reverse proxy, a 100 continue response is sent prematurely when a requ

[Bug 1641238]

2018-07-24 Thread Ylavic-dev
Thanks Jean-Frédéric, applied in r1836588. This is the same patch (plus a req != NULL check) rebased on latest trunk, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title: as a revers

[Bug 1641238]

2018-07-06 Thread Ylavic-dev
Yes please do, along with the httpd error_log with LogLevel trace7. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title: as a reverse proxy, a 100 continue response is sent premature

[Bug 1641238]

2018-07-06 Thread Ylavic-dev
Thanks Michael, at first glance the error_log is with mod_proxy_ajp, while attachment 34451 is about mod_proxy_http (and I'd like to keep the scope there for now). I agree that unpatched mod_proxy_http sends "100 continue" too soon (actually independently on the client and backend side). The pat