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

Daniel Lehman dlehman at esri.com
Thu Oct 23 09:21:54 CDT 2014

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 change removes the current custom port logic to instead use server->host_port to update the Host: field
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-wininet-remove-custom-port-handling-in-HTTP_HandleRe.patch
Type: application/octet-stream
Size: 3039 bytes
Desc: 0001-wininet-remove-custom-port-handling-in-HTTP_HandleRe.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20141023/00ab3700/attachment-0001.obj>

More information about the wine-patches mailing list