thanks. i ended up writing a quick subscriber package:
https://gist.github.com/1771046 it supports two methods: 1- migrates headers into the redirect ( I opted to use .extend instead of merge_cookies, because i already had to pull the cookie data ) 2- stashes the cookies into a "@cookie-xfer" space within the session, then populates it on new requests The caveat to the first method, is that Safari doesn't like it. The caveat to the second method, is that it's storing based on the "string" of the cookie -- so there's no 'uniqueness'. i put in a boolean for a uniqueness via the cookie name... but its not really "correct". if you don't have that in there, the session can build up and easily max out the header size for many web servers. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
