I've recently installed WebDAV app as part of a 5.0.27 and 5.5.54 install.
I also have it installed on 4.1.29.
When I access a page from a browser (e.g. Firefox), via:
http://localhost:8080/webdav on 4.1.29, it returns to me the page at
http://localhost:8080/webdav/index.html.
When I do
retaining the
ability to edit it via webdav there are people out there that do
this. The exact
configuration tends to depend on the TC, browser and webdav client
combination
you choose. Search the archives for tips.
Mark
-Original Message-
From: Brian K Bonner [mailto:[EMAIL
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
My mind was playing tricks on me. My last reply wasn't accurate. I'll do
more research. Thanks for the clarification.
Brian
- Forwarded by Brian K Bonner/paraware on 11/19/2004 03:40 PM -
Brian K Bonner/paraware wrote on 11/19/2004 03:37:01 PM:
That sounds like what I'm seeing. IE
-
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
Tomcat 4.1.29 does not seem to handle schema's in the jsp:root tag. It
throws the following error:
- Root Cause -
org.apache.jasper.JasperException: This absolute uri
(http://www.w3.org/2001/XMLSchema-instance) cannot be resolved in either
web.xml or the jar files deployed with this
Hello,
I'm seeing something wierd with 4.1.24. If I access an unprotected
resource after I am authenticated, I receive null from getUserPrincipal().
I am using the Coyote Http 1.1 connector, although I've tried it with the
old catalina Http 1.1 connector.
Here's the test case:
1) access the
, EVEN if
your are authenticated.
Regards,
Brian K Bonner wrote:
Hello,
I'm seeing something wierd with 4.1.24. If I access an unprotected
resource after I am authenticated, I receive null from
getUserPrincipal().
I am using the Coyote Http 1.1 connector, although I've tried
