[prev in list] [next in list] [prev in thread] [next in thread] 

List:       twsocket
Subject:    [twsocket] Fw: Redirection and port issues in ICS THttpCli
From:       "Florin Vancea" <fvancea () maxiq ! ro>
Date:       2003-11-26 7:20:12
[Download RAW message or body]

So I am moving this to the list.

If you're interested, a more thorough description with links is available at
http://open.maxiq.com/ics/

Not much of a patch there, but I'd like a fix to this going into the next
version.

Florin

----- Original Message -----
From: "Francois PIETTE" <francois.piette@overbyte.be>
To: "Florin Vancea" <fvancea@maxiq.ro>
Sent: Tuesday, November 25, 2003 7:07 PM
Subject: Re: Redirection and port issues in ICS THttpCli


> > maybe moving this discussion to the list.
>
> This is defenitely the way to go.
> Make your code available somewhere publicly so that interested peoples
> (including me) can see it without attaching it to a message mailed to the
> list.
>
> Thanks.
>
> --
> francois.piette@overbyte.be
> http://www.overbyte.be
>
>
> ----- Original Message -----
> From: "Florin Vancea" <fvancea@maxiq.ro>
> To: <francois.piette@overbyte.be>
> Sent: Tuesday, November 25, 2003 8:02 AM
> Subject: Redirection and port issues in ICS THttpCli
>
>
> > Dear Francois,
> >
> > I'm not sure if I should post this to list, especially since I suspect
no
> > attachments can be posted there. My apologies if it was inappropriate to
> > mail directly to you.
> >
> > I found some issues with port specification in "Host:" header and
> > translation of the port when receiving 302 (redirect) in beta code
> available
> > for download on ICS page.
> > Summary:
> > 1. redirections are performed by certain servers (namely Tomcat, at
least)
> > according to "Host:" header, but that header does not contain the port
in
> > THttpCli request, therefore the returned "Location:" is not the good
one.
> I
> > suspect that THttpCli should specify the port in the "Host:" header, at
> > least when it's different from proto's default.
> > 2. When going through a proxy FLocation is rebuilt after a 302 is
> received,
> > based on various situations, but _without_ the port, therefore the
problem
> > reappears when using a proxy, even if the above (1) is solved and the
> server
> > correctly returns "Location:".
> >
> > I hacked HttpProt into performing those steps differently and it works
for
> > me, but I cannot tell if what I've done does not impact other stuff. If
> you
> > want, I can send you the modified version, to incorporate the changes
into
> > future versions, or more elaborate details on the problem (maybe moving
> this
> > discussion to the list).
> >
> > Best regards,
> > Florin
> >
>
>



-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
[prev in list] [next in list] [prev in thread] [next in thread]