tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey Janner <Jeffrey.Jan...@PolyDyne.com>
Subject RE: httpd/Tomcat load balancing question
Date Thu, 23 Dec 2010 14:36:19 GMT


> -----Original Message-----
> From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
> Sent: Thursday, December 23, 2010 5:07 AM
> To: Tomcat Users List
> Subject: Re: httpd/Tomcat load balancing question
> 
> 2010/12/23 Pid <pid@pidster.com>:
> > On 23/12/2010 07:49, André Warnier wrote:
> >> Pid * wrote:
> >>> On 22 Dec 2010, at 23:38, André Warnier <aw@ice-sa.com> wrote:
> >>>
> >>>> Pid * wrote:
> >>>>> On 22 Dec 2010, at 23:02, Jeffrey Janner
> >>>>> <Jeffrey.Janner@PolyDyne.com> wrote:
> >>>>>> Definitely the culprit.  Now, I just have to convince the Dev
> team
> >>>>>> that they are, once again, a bunch of idiots.
> >>>>> Fail.
> >>>> Pid,
> >>>> why /do/ the "static objects" links embedded in the login page get
> >>>> back to the browser with a jsessionid appended ?
> >>>
> >>> <c:url is a JSTL tag which encodes a link.
> >>
> >> So in clear everyday English, for the benefit of the oppressed
> minority
> >> who does not speak JSTL fluently, the fact of encoding this link in
> the
> >> page as "<c:url something..>" is the reason why Tomcat (roughly
> >> speaking) modifies it to add the ";jessionid" bit, yes ?
> >> And if one were to remove the "<c:url .." tag from those links, it
> >> wouldn't, right ?
> >>
> >> And if so, why did you say "Fail" above ?
> >
> > I was referring to the "Definitely the culprit." statement.
> > Fail because encoding the links to static resources is unnecessary.
> >
> 
> because it interferes with caching.
> 
> But in general sense it also depends on how the static resources are
> served by the web application: if you do not encode session id in
> those URLs, then access to those resources should not require a
> session
> (there should be no filters that require a session, nor authentication
> constraints).
> 
> 

Thanks for all the insight guys.
Apparently, they are encoding to get the Context prepended to the url, instead of using getContextPath.
The name calling is because someone told them that the c:url tag is the new standard, so they
used it everywhere. In other words, brain not engaged, but fingers working.
In fact, having the context path prepended means I have to add an extra directory level for
the static content on the HTTPD server.
But yes, I don't see why the sessionid would be needed for any static content.
Jeff
__________________________________________________________________________

Confidentiality Notice:  This Transmission (including any attachments) may contain information
that is privileged, confidential, and exempt from disclosure under applicable law.  If the
reader of this message is not the intended recipient you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.  

If you have received this transmission in error, please immediately reply to the sender or
telephone (512) 343-9100 and delete this transmission from your system.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message