The webdav servlets are exactly the same, give or take a few formatting
differences.
There are difference between 4.1.x and 5.x in how requests for
http://host/webapp/ are handled.
Generally, you can use a context for webdav, or you can use it with a browser to
server content. Trying to mix the
Mark,
I understand the issue w/ contexts (and I believe I understand the issue
w/ not being able to handle JSPs), **but I don't understand why the base
behavior is different**.
Are you suggesting that the 4.1.x, 5.x is causing a difference in the
Webdav behavior that would prevent
To: Tomcat Users List
Subject: RE: WebDav behavior
Mark,
I understand the issue w/ contexts (and I believe I
understand the issue
w/ not being able to handle JSPs), **but I don't understand
why the base
behavior is different**.
Are you suggesting that the 4.1.x, 5.x is causing a difference
is that they don't handle redirects to
well (or at
all even...)
-Original Message-
From: Brian K Bonner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 7:21 PM
To: Tomcat Users List
Subject: RE: WebDav behavior
Mark,
I understand the issue w/ contexts (and I believe
-
From: Brian K Bonner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 7:21 PM
To: Tomcat Users List
Subject: RE: WebDav behavior
Mark,
I understand the issue w/ contexts (and I believe I
understand the issue
w/ not being able to handle JSPs), **but I don't
From: Brian K Bonner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 9:10 PM
To: Tomcat Users List
Subject: RE: WebDav behavior
OK, I probably need to start over.
I'd like to access content from http://localhost:8080/abc
with my browser
and be able to see the Index.html
I was able to map two contexts to the same docbase, one a normal web.xml
context (recognizing welcome files) and one that supported WevDAV ops
(producing directory lists). See this post:
( RE: Multiple contexts mapped to single docbase)
