Hey Mark-

Thanks for the quick reply, and what you're saying confirms my
assumption that the filter solution that is provided isn't going to
work for me.

However, I claim that the initial bug report is *exactly* the problem
I'm having.  If the filter solution doesn't address the problem, then
why was the report labeled fixed and closed?

Also, I'm not quite following what you're saying here (which could
mean I didn't explain my problem clearly):

The way the webdav servlet is written, it exposes the whole of the
webapp.

Agreed, that's what I'm finding and trying to avoid.

Mapping it to /edit/* allows the content to be exposed at an
alternative url.

Sure, but the content exposed would still be the "whole of the webapp", right?

The idea is that normal users access /your-app/*, a
system admin can edit contant via /your-app/edit/*.

Not following what a system admin has to do with anything.  The 'edit'
folder would just be implied ... both "normal users" and "system
admin" would still be exposed to the whole of the webapp, right?

On 6/30/07, Mark Thomas <[EMAIL PROTECTED]> wrote:
Robert J. Carr wrote:
> I'd like to add the webdav servlet to my own web application.  I can
> do this and it works, but it treats the root of my webapp as the root
> of the dav share.

The way the webdav servlet is written, it exposes the whole of the
webapp. Mapping it to /edit/* allows the content to be exposed at an
alternative url. The idea is that normal users access /your-app/*, a
system admin can edit contant via /your-app/edit/*.

To do what you want to do would require:
- changes to the webdav servlet
- placing the edtiable content in a separate (sub-)context
- blocking webdav methods for urls that should not be editable

Mark


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to