Opened 14 years ago

Closed 14 years ago

Last modified 12 years ago

#515 closed defect (duplicate)

dojo fails on certain sessionids within uris

Reported by: werpu@… Owned by: anonymous
Priority: high Milestone:
Component: Core Version: 0.2
Keywords: Cc:
Blocked By: Blocking:

Description

Following case: In the java servlet standard there is a standardized session handling (the same mechanism can be encountered outside of the javaworls as well)

uri;jsessionid=<sessionid>

the reason for this is the generation of a sessionid which then can be tracked in cookieless browsing sessions on the fly. In browsing sessions with cookies this is at least generated once for the cookie generation.

Anyway, if you have this id in all uris of the page even the dojo import the subsequent dojo requires start to fail if they have to download the files via the internal ajax infrastructure, due to a bug in dojo itself.

I am not sure how to bypass this except for a huge build and/or enforcing cookies within the browsers. Since this mechanism is also used outside of the java world for session tracking, it might have to be fixed on the dojo side.

Change History (3)

comment:1 Changed 14 years ago by alex

Milestone: 0.2.2release0.3.1
severity: criticalmajor

comment:2 Changed 14 years ago by jkuhnert@…

Resolution: duplicate
Status: newclosed

This duplicates #625 which gives a better explanation of what is happening.

comment:3 Changed 12 years ago by (none)

Milestone: 0.3.1

Milestone 0.3.1 deleted

Note: See TracTickets for help on using tickets.