My problem has reappeared. My first observation about the ;jsessionid=xxxx causing images not to load on the first page being Unix specific does not appear to be entriely correct. My development platforms are Windows based running only Tomcat. My test, demo, and production servers are all Linux running Apache as a front end to tomcat. It appears that Tomcat is able to correctly load the images even with the ;jsessionid=xxx appended to the end of the URL. It is when the request is handled by Apache instead of Tomcat that the image will fail to load.
I can not reliably recreate this problem. All that is required is to close all instances of my web browser and then access the site again. Stepping through the code with my debugger, I found that the problem occurs on line 535 of BaseURI. This is a call to response.encodeURL(). This is where the ;jsessionid=xxx is appended to the end. It appears that this is a tomcat specific problem. I see the same behavior on 4.1.12 and 4.1.24. The reason that we have not seen this become a problem before is the ContentURI (the older version of the pull tool) did not call response.encodeURL(). Without changing servlet containers, does anyone have any ideas on how I might overcome this issue? Granted, I can propbabley come up with a few nastly little hacks/workarounds but I am trying to avoid that sort of thing. > -----Original Message----- > From: Quinton McCombs [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 18, 2003 4:30 PM > To: 'Turbine Users List' > Subject: RE: Possible problem with the new URI code > > > 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
