Re: HTTP::Cookies with LWP::UserAgent

[Vynce]

yes, i think some websites do set and read the same cookie on one request.

I think the idea is to set and then immediately test a cookie as a method of checking to see if the user accepts cookies. then the server can make theoretically intelligent decisions about what else to do based on this data (e.g., us ealternate methods of keeping track of the user if cookies aren't working)

[alfie]

Although this has nothing to do I don't get it how it should be possible with the HTTP-Protokoll? There are 2 parts in a HTTP-Request: The request from the client to the server, and the response from the server back to the client. Given the fact that the server sends the cookie in his response how should the client somehow know "before" receiving if the server wants to know about a cookie?

Only posibility for this I can see: An <img src="/cgi-bin/cookiecheck.pl"> script in that page. Personally I don't think that this is really functional for clients might turn image-loading off, and/or they don't send the cookie back because they just have received it and the user still might have a "Do you want to store this cookie?" window above it's client while the client finishes loading the page in the background. Or is this broken behavior and I'm just thinking queer?

Anyway, my point still is: It can't be done on a single request, there must at least be two of them. One to send the cookie and the next one that can check if the cookie is set.
--
use signature; signature(" So long\nAlfie");