yes, that's what I meant.<br>so, I'm afraid we should also control where to bake cookie if adding support for path attribution to C::P::S::State::Cookie.<br><br><div><span class="gmail_quote">2006/8/4, <a href="mailto:Wade.Stuart@fallon.com">
Wade.Stuart@fallon.com</a> <<a href="mailto:Wade.Stuart@fallon.com">Wade.Stuart@fallon.com</a>>:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Sorry to respond to myself, but I just reread your message and I may have<br>misunderstood. If you mean that you set the cookies path attr to /abc<br>from a request to /, that is disallowed from the rfc.<br><br>4.3.2
Rejecting Cookies<br><br> To prevent possible security or privacy violations, a user agent<br> rejects a cookie (shall not store its information) if any of the<br> following is true:<br><br> * The value for the Path attribute is not a prefix of the request-
<br> URI.<br><br><br>a cookie path of '/abc' can be set from a request to /abc/ or any url under<br>that prefix, but not '/' or '/xyz' ...<br>_______________________________________________<br>Catalyst-dev mailing list
<br><a href="mailto:Catalyst-dev@lists.rawmode.org">Catalyst-dev@lists.rawmode.org</a><br><a href="http://lists.rawmode.org/mailman/listinfo/catalyst-dev">http://lists.rawmode.org/mailman/listinfo/catalyst-dev</a><br></blockquote>
</div><br>