mirror of
https://github.com/curl/curl.git
synced 2026-08-26 20:23:32 +03:00
Fixed a flaw in the "Expect: 100-continue" treatment. If you did two POSTs
on a persistent connection and allowed the first to use that header, you could not disable it for the second request.
This commit is contained in:
parent
c410769588
commit
a4ebf5b507
5 changed files with 21 additions and 21 deletions
|
|
@ -1532,14 +1532,14 @@ CURLcode Curl_readwrite_init(struct connectdata *conn)
|
|||
Thus, we must check if the request has been sent before we set the
|
||||
state info where we wait for the 100-return code
|
||||
*/
|
||||
if (data->set.expect100header &&
|
||||
if (data->state.expect100header &&
|
||||
(conn->proto.http->sending == HTTPSEND_BODY)) {
|
||||
/* wait with write until we either got 100-continue or a timeout */
|
||||
k->write_after_100_header = TRUE;
|
||||
k->start100 = k->start;
|
||||
}
|
||||
else {
|
||||
if(data->set.expect100header)
|
||||
if(data->state.expect100header)
|
||||
/* when we've sent off the rest of the headers, we must await a
|
||||
100-continue */
|
||||
k->wait100_after_headers = TRUE;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue