Servlets Sending WEBDAV Requests(i.e. PROPPATCH) Work in Tomcat 4.x but not Tomcat 5.x +

[Jason Kong <jk...@i4i.com>]

Greetings

My Company has a number of servlets that communicate with each other using
Webdav requests, in particular
Requests containing the PROPPATCH verb. Under the tomcat 4.x environment,
there is no issue, but once under tomcat 5.x or even tomcat 6.x, the
requests fail (although no exceptions are thrown, the response is HTTP 200
even!)

Does anyone have a work-around and possibly an explanation?

Thanks in advance

JK



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

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

Re: Servlets Sending WEBDAV Requests(i.e. PROPPATCH) Work in Tomcat 4.x but not Tomcat 5.x +

[Mark Thomas <ma...@apache.org>]

Jason Kong wrote:
> Greetings
> 
> My Company has a number of servlets that communicate with each other using
> Webdav requests, in particular
> Requests containing the PROPPATCH verb. Under the tomcat 4.x environment,
> there is no issue, but once under tomcat 5.x or even tomcat 6.x, the
> requests fail (although no exceptions are thrown, the response is HTTP 200
> even!)
> 
> Does anyone have a work-around and possibly an explanation?

The behaviour you describe does not agree with the source for the webdav
servlet (which is the same across all Tomcat versions). The source for
doPropPatch() is:

    protected void doProppatch(HttpServletRequest req,
                               HttpServletResponse resp)
        throws ServletException, IOException {

        if (readOnly) {
            resp.sendError(WebdavStatus.SC_FORBIDDEN);
            return;
        }

        if (isLocked(req)) {
            resp.sendError(WebdavStatus.SC_LOCKED);
            return;
        }

        resp.sendError(HttpServletResponse.SC_NOT_IMPLEMENTED);

    }

Therefore I would never expect to see this work and certainly wouldn't
expect to see a 200. Maybe a configuration issue?

HTH,

Mark



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