Bug #1342
closedPaths for session cookie
0%
Description
Hi,
It seems that you create a session cookie you do it like this;
Set-Cookie: /hello.cgi=h30vvJtxLCTpBsfY; Version=1;
Notice that it doesn't have any Path, and so the browser will add a Path itself, and uses the directory of the request.
There is a problem when the user starts in some internal path, and the browser adds that path internal path. It of course doesn't send the cookie when navigating to a different path.
I suggest you send the path based on the name of the application with the name of the binary removed, so "/hello.cgi" becomes "/".
KD Updated by Koen Deforche about 14 years ago
- Status changed from New to Feedback
- Assignee set to Koen Deforche
Hey,
is this bug superseded by #1343 ?
Regards,
koen
KR Updated by Kurt Roeckx about 14 years ago
No, it's unrelated. This is about a cookie you generate yourself somewhere, probably not using setCookie(). The other is about a cookie I generate using setCookie. The one I generate does have a path, but by default is the wrong one. This bug is about your cookie and that it doesn't have a path.
KD Updated by Koen Deforche about 14 years ago
- Status changed from Feedback to Resolved
- Target version set to 3.2.2
Hey Kurt,
Indeed so. Although I really advise against using cookies for session tracking since this will cause problems when opening multiple windows/tabs to the same Wt application.
Regards,
koen
KR Updated by Kurt Roeckx about 14 years ago
Koen Deforche wrote:
Hey Kurt,
Indeed so. Although I really advise against using cookies for session tracking since this will cause problems when opening multiple windows/tabs to the same Wt application.
I use "Auto" for the tracking. You suggest I change it to "URL"? As far as I know this is an internal thing of Wt to track the tab/window.
Kurt
KD Updated by Koen Deforche about 14 years ago
- Status changed from Resolved to Closed
Released in Wt 3.2.2