On 06/26/2007 06:58 AM, Grant wrote: >> > I think (I'm not digging into the code ATM so I don't know for sure) >> > that the bounce happens afterwards, but it overrides all the buffered >> > output from anything previous so cookies that were meant to be sent >> will >> > get lost. The best way to keep the session on a bounce is to generate >> > the bounce link properly with the session ID in the link. >> > >> > We should have some sort of parameter for bounce that will preserve >> cookies. >> > >> Just bounce to the page, rather than to a full URI: >> >> [bounce page=index status=301] >> >> The URI will be generated with a session ID parameter if no cookie is >> detected. > > The problem with that is I use: > > ScratchDefault mv_no_session 1 > > which basically requires session cookies and doesn't write IDs to the > URL. Is there any way to use mv_no_session and prevent the extraneous > session from being created? Use mv_no_session_id and mv_no_count instead, then it will have the id in links until it detects a cookie. This gives the best of both worlds as it means that your site will still work for people who don't have cookies turned on. Peter _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.