<br><br><div><span class="gmail_quote">On 8/2/06, <b class="gmail_sendername">islue</b> <<a href="mailto:islue.hu@gmail.com">islue.hu@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Is it necessary to limit baking the cookie where the path is matching only?</div></blockquote><div><br>The point isn't to limit when/if we bake the cookie. The "path" attribute of a cookie tells the browser what paths to send it back to us for. So if you have a cookie called "session_id", and your app is at
<a href="http://myhost/catapp">http://myhost/catapp</a>, and there's another application hosted at <a href="http://myhost/otherapp">http://myhost/otherapp</a> which also has a "session_id" cookie, you'll definitely need this to avoid them stepping on each other. If the root of the domain (
<a href="http://myhost/">http://myhost/</a>) and everything beneath it is all served just by your Catalyst app, then I guess one wouldn't care about it.<br><br>-- Brandon<br></div><br></div>