https://issues.apache.org/bugzilla/show_bug.cgi?id=46709
Summary: Expect: 100-continue to an HTTP/1.0 server change Breaks
.NET Web Services
Product: Apache httpd-2
Version: 2.3-HEAD
Platform: PC
OS/Version: Linux
Status: NEW
Severity: regression
Priority: P2
Component: mod_proxy
AssignedTo: [email protected]
ReportedBy: [email protected]
Our environment uses a HTTP 1.1 mod_proxy server with 1.0 back-end webs. This
is for various compatibility reasons, but in order to make this arrangement
work in versions of Apache after 2.2.10 due to this change:
*) mod_proxy_http: Do not forward requests with 'Expect: 100-continue' to
known HTTP/1.0 servers. Return 'Expectation failed' (417) instead.
[Ruediger Pluem]
This change breaks .NET web service clients that use Expect: 100-continue by
default when initiating a session. To Replicate, attempt to connect to a proxy
setup similar to the one mentioned above with any web service url hosted by a
back-end web. The connection will fail due to the Expectation failed response.
Regardless of what the RFC declares, this worked previous to the change. We
have been patching manually just by applying the below simple patch:
--- mod_proxy_http.c.orig 2009-02-12 18:35:55.000000000 -0500
+++ mod_proxy_http.c 2009-02-12 18:35:26.000000000 -0500
@@ -703,10 +703,11 @@
* According to RFC 2616 8.2.3 we are not allowed to forward an
* Expect: 100-continue to an HTTP/1.0 server. Instead we MUST return
* a HTTP_EXPECTATION_FAILED
- */
+ * Disabled for .NET clients
if (r->expecting_100) {
return HTTP_EXPECTATION_FAILED;
}
+ */
p_conn->close++;
} else {
buf = apr_pstrcat(p, r->method, " ", url, " HTTP/1.1" CRLF, NULL);
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
