Have never used the tomcat webdav servlet. I use the slide webdav servlet. I thought i needed to correct your suppositions and mistakes in handling protocol. En l'instant précis du 23/07/07 12:31, Johnny Kewl s'exprimait en ces termes: > For future reference.... the WEBDAV problems between Microsoft and Tomcat > seem to be as follows.... > First thanks for pointing me to the MS patch, although like the other > poster > said... it didnt help, or maybe it did, but only on the MS side. > > **** MICROSOFT doesnt like the lagging folder slash.... **** > Tomcats mapping wants you to use a slash at the end.... ie webapp/webdav/ > When the MS webfolder client sends a request, it drops that lagging > slash.... and tomcat promptly tells it to get lost.... see below for > actual > web conversations Tomcat should not refuse webapp/webdav if you have a mapping to /webdav/*. It should at least dispatch to servlet mapped on /webdav/*. I have a slide webdav servlet mapped to /DAV/* and MS webfolder can mount it without major troubles. However, maybe the tomcat servlet does not recognize request properly when there is no trailing slashes. Then it should be fixed to handle properly the root. > > Ok... this is not too big a problem to solve... I created a servlet > mapped > to > /webapp/webdav/start (no lagging slash) and dispatched the requests > off to > /webapp/webdav/ > This solves the lagging slash problem... so now MS and tomcat will > actually > talk > > **** Tomcat thinks Microsoft is an alien ****** > > But unfortunately, tomcat thinks microsoft is asking stupid questions and > really craps all > over MS..... "PROPFIND is not defined in RFC 2068".... go play with > yourself > MS ;) > > It (PROPFIND) does actually seem to be defined in > http://www.ietf.org/rfc/rfc2518.txt > and it seems MS was the main modifier of the RFC.... You redirecting servlet does not handle the propfind method. You probably only implemented GET/POST in your servlet. Other methods are handled by the default generic servlet behaviour which is some sort of "unrecognized command" message. To handle all kind of http methods in your servlet, override the following method: protected void service(HttpServletRequest req, HttpServletResponse resp) Receives standard HTTP requests from the public service method and dispatches them to the doXXX methods defined in this class. It's not tomcat container job's to handle rfc2518 but it's the servlet's job. > > So there you have it.... RFC 2068 is now too old.... because it seems MS > just had the spec changed and didnt bother with any compatibility... like > role back to 2068 if a new feature failed. You get it wrong, 2068, is simple http (GET/POST/PUT/OPTIONS). 2518 is WEBDAV protocol (PROPFIND, PROPPATCH, multi status responses, etc). No webdav client would be able to handle a simple http server. It need webdav commands to be available and server to send proper webdav responses. That has nothing to do with MS. > I dont know anything about webdav, it could be the old rfc was > impossible to > make work with the system shell, or they just figured, stuff it, we the > desktop standard anyway, we'll do it our way..... hey Bill, change the > spec > ;)... who knows? > > Anyway it seems 2 things need to happen.... tomcat needs to be brought > up to > the current rfc, and all MS users out there beg the developer to please > allow it to work with and without the lagging slash.... then I think life > will be good in webdav lane ;) > > As it stands.... it will never work with MS webdav servlet should be able to respond to requests without trailing slashes. If not it should be fixed. There is no reason webapp/webdav/ and webapp/webdav would provide different responses. > <snip>
-- http://www.noooxml.org/ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
