Yes, something is wrong. I also just compiled v8 and the OverbyteIcsHttpTst demo as well.
If you GET this URL: http://www.htmlvalidator.com/test/cookies/test-redirect.php Then you get "Server port is 80." with the ICS demo, but put the same URL in a browser and you get "Server port is 8080.", so ICS is not handling the port change correctly, nor is it indicating the port in the Location property. I've been using ICS for a while and this never came up until someone using non-standard ports & redirection on their development server reported this issue. I'd really like a fix for this. I'm not sure who I should contact about getting this resolved in the code base? Thanks, Albert Wiersch > -----Original Message----- > From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On > Behalf Of RTT > Sent: Monday, December 10, 2012 10:40 AM > To: ICS support mailing > Subject: Re: [twsocket] Did I find a bug in THttpCli? > > > I tested with current ICSv8/v7 and it works perfectly (checked with > Wireshark). > > The only problem is that property Location doesn't include the non-default > > port number. A workaround would be to get the Location header manually. > > > > In a browser I get an html that says: > Server port is 8080. > > With ICSv8 OverbyteIcsHttpTst I get an html that says: > > Server port is 80. > > So something is working differently. > > -- > 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 -- 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
