group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #33497
[Bug 1641238] Re: as a reverse proxy, a 100 continue response is sent prematurely when a request contains expects: 100-continue
Since this is fixed in 2.4.40, that means eoan and focal have the fix already, since they are at 2.4.41.
Confirmed in the CHANGES file:
"""
Changes with Apache 2.4.40
...
*) mod_proxy_http: forward 100-continue, and minimize race conditions when
reusing backend connections. PR 60330. [Yann Ylavic, Jean-Frederic Clere]
"""
** Changed in: apache2 (Ubuntu Eoan)
Status: Triaged => Fix Released
** Changed in: apache2 (Ubuntu Focal)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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
Status in Apache2 Web Server:
Fix Released
Status in apache2 package in Ubuntu:
Fix Released
Status in apache2 source package in Trusty:
New
Status in apache2 source package in Xenial:
New
Status in apache2 source package in Bionic:
New
Status in apache2 source package in Disco:
Triaged
Status in apache2 source package in Eoan:
Fix Released
Status in apache2 source package in Focal:
Fix Released
Bug description:
This effects trusty, xenial and current httpd trunk.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60330
As a reverse proxy, a 100 continue response is sent prematurely when a
request contains expects: 100-continue. This causes the requesting
client to send a body. The apache httpd proxy will then read the body
and attempt to send it to the backend, but the backend already sent an
error and should be allowed to NOT read the remaining request body,
which never should have existed. When the backend does not read the
request body mod_proxy_pass errors and returns a 500 error to the
client. The client never receives the correct error message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1641238/+subscriptions