On Fri, 26 Oct 2001, Paul Harrington wrote:

> Hmm the code should deal with this too. I'm wondering if this is
> something to do with reusing the connection.

Yes, this output certainly indicates that possibility.

> Location: /online/1,1795,Welcome,00.html?logout=TRUE

> * Connection (#0) left alive
> * Follows Location: to new URL:
> * 'https://fred.rhl:9004/online/1,1795,Welcome,00.html?logout=TRUE'

At least this shows us that the following is working fine.

> But it doesn't return the page we are meant to be redirected too.

Do you have access to the server in question? I mean, does the server log
anything interesting regarding that second request which it doesn't return
anything to.

Hm, this simple test case you made doesn't pass the cookies back after the
follow. Could that be the reason? Not very likely, as a good server should
always return at least a set of headers...

> Getting the page manually using curl works fine.

Could it be a server-related problem with persistant connections and SSL?

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/