Cookies are supposed to be sent back only to the server that set them, but you are depending on the browser for the determination of where to send them. Some older browsers would let you set a cookie to be sent back to domain '.com.', with the result of sending the cookie back to any .com server it contacted. People rolling their own spider code will frequently copy the Cookie headers from a test request without bothering to find out what they mean, resulting in odd cookies being sent to web servers everywhere. Some anonymizing or sanitizing proxies will replace cookies that are commonly used for tracking browsers with versions that contain random identifiers, so the site will not give them a cookie error, but will also not get any useful information from the cookies they attempt to set. So although it is rare for cookies to actually 'leak', there are all kinds of fringe cases that can result in you getting strange cookies.
| We're not surrounded, we're in a target-rich environment! |
|---|
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
