On 11/29/2012 2:14 PM, Caldarale, Charles R wrote:
From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
Subject: Context Path for a subdirectory
If I have a webapp, with a www directory, and in that www directory
are other directories, how would I restrict access to one of those
subdirectories to the localhost?
Probably your best bet is to use a filter for the webapp to which those
subdirectories belong.
Is the context path of directory1: /webapp1/directory1
No, it's /webapp1/www/directory1.
Would I create a context named directory1.xml such as the following?
Absolutely not. A webapp can never be nested inside another, so what you're
trying to do is nonsensical.
- Chuck
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.
-Terence Bandoian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org