Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50B90E20.2000907@tmbsw.com>
References: 
 <99C8B2929B39C24493377AC7A121E21FC4947E68A3@USEA-EXCH8.na.uis.unisys.com>
	<50B90E20.2000907@tmbsw.com>
Date: Sun, 2 Dec 2012 14:54:45 +0400
Message-ID: 
 <CABzHfVng3dfOYAPAyCB0CGMPd=FFB5wq9-SRLZy44NsPOeGG5g@mail.gmail.com>
Subject: Re: Context Path for a subdirectory
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2012/11/30 Terence M. Bandoian <terence@tmbsw.com>:
> Hi, Chuck-
>
> I don't mean to be argumentative but, with Tomcat 6.0.29, I found that
> static files from an images subdirectory of a web application were not
> cached by Internet Explorer 7.  As a workaround, I created a context for the
> images subdirectory and left it nested in the web application.  The files
> from that directory were then cached by IE7.  The difference was that the
> following response headers were included when there was no separate context
> defined for the subdirectory:
>
> Pragma: No-cache
> Cache-Control: no-cache
> Expires: Wed, 31 Dec 1969 18:00:00 CST
>
> Something else I found unusual was that ETag and Last-Modified headers were
> provided in both configurations.  Apparently, some browsers (e.g. Firefox)
> utilize that information even when the no-cache and Expires headers are
> provided.
>
> I realize this is a non-standard configuration but it worked with 6.0.29 and
> 6.0.35.
>


The "no-cache" headers are added to resources that are protected by a
security constraint.   That is for an obvious reason: if a resource is
cached locally, you cannot protect it.

It is usually a good idea to do not protect such static files.


Regarding "a.war/foo/bar" vs "a#foo.war/bar",  Tomcat always selects a
webapp first - one that matches the longest path. Then it selects a
resource in the selected webapp.

It is mentioned in the Introduction section of the
"config/context.html" page of the Configuration Reference Guide.

One example of using this rule is ROOT/admin/index.html page in Tomcat 5.5.

When a user requests "http://localhost:8080/admin/" and the admin
webapp is not installed, the ROOT/admin/index.html page is called and
says that "no such application is here".  If the admin webapp is
installed, then its welcome page (admin/index.jsp) is displayed.

Best regards,
Konstantin Kolinko

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