- Bug report #1025986. When following a Location: with a custom Host: header
replacement, curl only replaced the Host: header on the initial request and didn't replace it on the following ones. This resulted in requests with two Host: headers. Now, curl checks if the location is on the same host as the initial request and then continues to replace the Host: header. And when it moves to another host, it doesn't replace the Host: header but it also doesn't make the second Host: header get used in the request. This change is verified by the two new test cases 184 and 185.
This commit is contained in:
13
CHANGES
13
CHANGES
@@ -6,6 +6,19 @@
|
||||
|
||||
Changelog
|
||||
|
||||
Daniel (10 September 2004)
|
||||
- Bug report #1025986. When following a Location: with a custom Host: header
|
||||
replacement, curl only replaced the Host: header on the initial request
|
||||
and didn't replace it on the following ones. This resulted in requests with
|
||||
two Host: headers.
|
||||
|
||||
Now, curl checks if the location is on the same host as the initial request
|
||||
and then continues to replace the Host: header. And when it moves to another
|
||||
host, it doesn't replace the Host: header but it also doesn't make the
|
||||
second Host: header get used in the request.
|
||||
|
||||
This change is verified by the two new test cases 184 and 185.
|
||||
|
||||
Daniel (31 August 2004)
|
||||
- David Tarendash fount out that curl_multi_add_handle() returned
|
||||
CURLM_CALL_MULTI_PERFORM instead of CURLM_OK.
|
||||
|
||||
Reference in New Issue
Block a user