AW: WebDav - mapping question? 2007-07-24 - By Konstantin Breu
Back
Hello,
maybe a filter, mapped to /* could look for requests to /webdav, and then
send the direct response (OPTIONS/PROPFIND,....), instead of 302. This could
be a workaround. There is also the problem with some MS clients, which do
requests to / (first of all OPTIONS requests). This could also be solved by
a filter. The filter would be an additional part of the webdav servlet, to
be used as "MS workaround"...
Cheers,
Konstantin
-- --Urspr?ngliche Nachricht-- --
Von: Mark Thomas [mailto:markt@(protected)]
Gesendet: Dienstag, 24. Juli 2007 01:36
An: Tomcat Users List
Betreff: Re: WebDav - mapping question?
David Delbecq wrote:
> Tomcat should not refuse webapp/webdav if you have a mapping to
> /webdav/*. It should at least dispatch to servlet mapped on /webdav/*.
Tomcat doesn't reject requests of this type . For any directory
resource without a trailing '/' it will do a 302 redirect and add '/'.
The MS client doesn't seem to be able to handle the redirect. This is
probably the cause of the problem. I tried raising this with MS and
got nowhere.
Because of where Tomcat does this redirect, I can't immediately see a
way around this. I'll have a think over the next few days.
Mark
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
