On Thursday, October 10, 2013 4:50 PM [GMT+1=CET],
Albert Wiersch wrote:

>> I just checked in a fix with Log:
>> "Fixed a relocation bug with URL "https://yahoo.com"; by removing
>> port "443" from the Host-header, otherwise relocation header
>> returned by the server had that port appended as well even though
>> the new location was simple HTTP."
>> 
>> Search for "8.05" :
>> http://svn.overbyte.be:8443/svn/ics/trunk/Source/OverbyteIcsHttpProt.pas
> 
> Thanks Arno!
> 
> So was this ultimately a yahoo relocation bug for including port 443
> on the Location header?

I do not know for sure as I do not know for sure whether it was a bug 
in ICS. 
I noticed that other clients actually received a location header without
the 443 port and they did not sent the port with the host header.
Don't know whether or not that's mandatory. In RFC 2616 I just found one
related sentence:
"A "host" without any trailing port information implies the default port 
for the service requested (e.g., "80" for an HTTP URL)."

So at least my fix is actually RFC compliant.  

-- 
Arno
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to