(In reply to Yann Ylavic from comment #14) > Thanks Michael, at first glance the error_log is with mod_proxy_ajp, while > attachment 34451 [details] 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 patch is precisely to avoid that (hop by hop 100-continue handling), did > you give it a try? If yes, could I have the error_log with mod_proxy_http?
I agree, I have tried all possible modules with the same negative result. I will redo for you. Moreover, I will compile from trunk along with your patch and try to reproduce. Does it still apply cleanly to trunk? Please be patient, I won't be able to test anything before 2018-07-23. Thank you. -- 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 request contains expects: 100-continue To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1641238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
