Hello, Jonathan.
Unfortunately you can't know where a cookie was defined because they are sent
through the following HTTP header:
Cookie: cookie1=value1&cookie2=value2
Which doesn't specify the host where they were defined.
Cheers.
On Monday February 23, 2009 21:17:31 Jonathan Vanasco wrote:
> i've got an annoying issue with cookies...
>
> in my setup, i unfortunately had some cookies baked with www.domain.com
> and others with domain.com
>
> this didn't cause an issue in pylons, but it did cause an issue in a
> section of the site that was offloaded to php ( which was running a
> blog, and blocking if there was no preview cookie ).
>
> to consolidate things, I dropped www off our website, and am piping
> things through domain.com exclusively
>
> i have a few users with stray www.domain.com cookies that pylons is
> reading -- is there an easy way to invalidate these through pylons ?
>
> everything that i'm seeing in response.cookies is just k/v - there's
> no domain or other info.
> i can't remember if the domain info is supposed to be sent with
> cookies or not.
>
> anyone have a clue ?
>
--
Gustavo Narea <http://gustavonarea.net/>.
Get rid of unethical constraints! Get freedomware:
http://www.getgnulinux.org/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
