[PATCH] wininet: remove custom port handling in HTTP_HandleRedirect (try 3)

Daniel Lehman dlehman at esri.com
Fri Oct 24 18:16:15 CDT 2014

Try 3:
	- changed patch subject to more accurately reflect the point of the patch
	- fix wine test.  I was blindly replacing the Host field with the appended host_port, which is only needed if a custom port is used

Try 2: rebased

HTTP_HandleRedirect updates both:
- the Host: field
- and session->hostname

If there is a custom port, it is appended to session->hostName.  This causes problems for later HttpOpenRequest/process_host_port calls that append the port to the host name (resulting in "foobar:1234:1234")

There is already logic in HTTP_HandleRequest that will update the request->server if the new host or port don't match.  in that case, get_server/process_host_port use the updated host and port and store them appended in server->host_port.  If they already match, server->host_port is left untouched

The attached (and updated) change replaces the Host field with the combined host_port if a custom port is used, or just the server name for a standard port
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-wininet-don-t-append-custom-port-to-session-host-nam.patch
Type: application/octet-stream
Size: 2005 bytes
Desc: 0001-wininet-don-t-append-custom-port-to-session-host-nam.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20141024/0da8c038/attachment.obj>

More information about the wine-patches mailing list