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.
signature(" So long\nAlfie");
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.