On Fri, 11 May 2001, Keller, Bryan wrote:

(Please don't take the thread off the list, I'm sure other people will want
to know...)

> I'm hitting a server that requires authentication. After authenticating,
> the server sets 3 cookies, and sends you to a login function of the
> application (via Location: header). The login function takes one of the
> cookies, does some logic to figure out what's available to you, and sends
> you a page using the META REFRESH tag.
>
> My problem is that if I parse the refresh, and call another instance of
> curl, the server attempts to authenticate me again and sends me to the
> login function again, rather than giving me the page.
>
> I guess the question is: is there a way in curl to maintain my
> authenticated status (like a browser would do), when I request the page
> specified in the refresh tag?

Well, it depends on what "authenticated status" means. I guess that if a
browser can "maintain it", then so can we.

I would guess that this maintaining is simply a matter you sending back the
correct set of cookies, as that is how lots and lots of web based apps keep
authentication status between multiple requests.

And then, you need to pass the set of cookies to curl (the ones you received
after the login) when you request the 'refresh'-page.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
_______________________________________________
Curl-and-php mailing list
Curl-and-php_at_lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/curl-and-php