The picture is correct, but you don't have to use an own servlet to serve the static pages.
Define all static pages as JSP's and use encodeURL on all ebedded URL's. > -----Urspr�ngliche Nachricht----- > Von: Kevin McBrearty [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 6. Dezember 2001 19:57 > An: [EMAIL PROTECTED] > Betreff: Question re: static/dynamic content, cookies, > session tracking > > > I just want to clarify my understanding of something here. > > I have a web application which serves both static and dynamic > pages, and > the user can move back and forth between static and dynamic > pages. The > dynamic pages are generated by servlets using Velocity. > Session tracking > is involved, and this works fine when cookies are enabled on the > browser. The problem is when cookies are disabled and the user moves > from a dynamic page to a static page and back again. My > understanding > is that URL rewriting is the responsibility of the > application, not the > web server, so that to maintain session tracking between static and > dynamic pages when cookies are disabled means that I would > have to serve > all pages, both static and dynamic, from a servlet and use > encodeURL to > properly encode the links to and from the static pages. > > Is this correct or am I missing something very fundamental here ? > > -- > Kevin McBrearty > ATG Automation Technologies Group Ltd. > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
