Incorrect handling of the 100 (Continue) Status
Lighttpd currently does not handle section 8.2.3 of the HTTP/1.1 spec correctly (it always responds with HTTP/1.1 417 Expectation Failed). As a result many common HTTP/1.1 clients cannot POST data to lighttpd based web servers. (mshtml, Visual Studio, libcurl, HttpClient, HttpWebRequest)
Please see section 8.2.3 of
support Expect: 100-continue with HTTP/1.1 requests
Ignore config option server.reject-expect-100-with-417;
server.reject-expect-100-with-417 will be removed in a future release.
"Incorrect handling of the 100 (Continue) Status"
"'Expect' header gives HTTP error 417"
"Improve DAV support to be able to handle git as a client"
"Change server.reject-expect-100-with-417 from flag to regular expression matching the URL"
Updated by gstrauss over 1 year ago
- Description updated (diff)
- Status changed from Wontfix to Patch Pending
- Target version set to 1.4.45
Transfer-Encoding: chunked is supported in lighttpd 1.4.44
Expect: 100-continue will be supported in lighttpd 1.4.46
This will replace the current behavior of sending 417 Expectation Failed, which is RFC compliant, but not very friendly, if server.reject-expect-100-with-417 = "enable", which is the default for some historical reason. (See #1017)
Also available in: Atom