I only see the session id on the page following my login page and only
for the very first session that is created for the context. I have
never seen the session id added to the urls that are generated for
images - but then I am using the turbine 2.2 uri code.
I had a view in the past that this was somehow a container issue (i.e. tomcat or whatever you are using). This was based on my observation that the session id was not displayed in this manner when I was using jetty (while I do observe this behaviour using tomcat-4.1.24, having a bit of a play with this right now I can't seem to reproduce the behaviour locally, only from my remote server).
So without offering anything concrete in the way of help, I think my observations may support your conjecture - i.e. that the new uri code is getting the session id as part of the base uri for the site when the container is providing it.
Cheers,
Scott
Quinton McCombs wrote:
The problem has just become a bit more strange.
On the first visit to the application, it is common to see the
;jsessionid=xcxxxx stuff.
On my test server I started noticing that the images were not loading on the login screen. When I looked at the source for the page, I discovered that the URL for the image had ;jsessionid=xxxxx appended to it. Curiously, this does not present a problem on a Windows platform. On Unix, the image is not returned to the browser.
My production server is running a slightly older version of Turbine and uses the older ContentURI tool. It does not generate the image URLs with the ;jsessionid=xxx at the end even on the first visit to the app.
Now... About getting more stange. In an attempt to try and track down the problem, I started stepping through the code with my debugger. I made sure to clear my cookies and cached web pages from the browser. I also restarted Turbine. As I stepped through the code, I did not see the URLs being returned from ContentTool.getURI having the ;jsessionid=xxx at the end. I go back and look at the source for the generated page and the URLs have been generated correctly.
It appears, that I intimidated the code by pulling out the debugger. Everything works correctly now. I wonder though.... Perhaps, it will get brave again in the future and decide to start generating URLs incorrectly again.... ;-)
--------------------------------------------
Quinton McCombs
NequalsOne - HealthCare marketing tools
mailto:[EMAIL PROTECTED]
http://www.NequalsOne.com
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 3:58 PM
To: [EMAIL PROTECTED]
Subject: RE: Possible problem with the new URI code
Do you need the jsessionid stuff? Or is it attempting to go to a login page since you don't have it, which would cause I guess extra records in your web logs?
Eric
-----Original Message----- From: Quinton McCombs [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 4:57 PM To: [EMAIL PROTECTED] Subject: Possible problem with the new URI code
I have noticed a strange problem that I think might be related to the new URI code. When using ContentTool to generate a URI for images, stylesheets, etc, I not get the ;jsessionid=xxxxxx appended to the end of the URL. This is causing my images not to load. Of course, hitting refresh on the browser fixes this problem.
Any ideas?
--------------------------------------------
Quinton McCombs
NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] > http://www.NequalsOne.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au [EMAIL PROTECTED] Mobile: 0403 278 908
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
