|
|
Posted by Darko on 11/09/07 22:57
On Nov 9, 11:10 pm, "Sanders Kaufman" <bu...@kaufman.net> wrote:
> "Darko" <darko.maksimo...@gmail.com> wrote in message
>
> news:1194644890.091070.8510@v2g2000hsf.googlegroups.com...
>
> > I'm not sure, but I also think redirection is the problem. When you
> > visit a page that sets session values,
> > the page automatically transmits the session id in cookies. However,
> > if you redirect the user in the header,
> > I don't think the browser will bother to read and place the cookies
> > locally, but will automatically cancel
> > everything and go to the given address. So, you should try sending
> > <meta> redirection directives instead of
> > this, or use Javascript, whatever.
>
> I would expect that a META would have the same cookie effect as a header().
> That's why it uses the attribute "http-equiv".
> I'd be interested to hear if that's how it worked out.
I'm not sure, really. I didn't use it for a long time; from the time I
hadn't used
sessions :)
Although, I know that the page in that case does get completely loaded
and even
shown in the browser, so I reckon maybe the cookies still -get- read,
but it
should be tested.
Until then, Ezechiele should try it with Javascript, just to make sure.
Navigation:
[Reply to this message]
|