Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Date: Tue, 3 Aug 2004 12:06:10 -0300
Sender: spencer@infointeractive.com
From: Brad Spencer <spencer@infointeractive.com>
To: users@httpd.apache.org
Message-ID: <20040803150610.GB28947@eng.infointeractive.com>
Mail-Followup-To: users@httpd.apache.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: [users@httpd] Apache 2.0.48 mod_dav interaction with Expect:
 100-continue

I've been unable to determine what the "proper" interaction is between
WebDav and the "Expect: 100-continue" functionality should be.  When
using Apache 1.3 with a third-party mod_put a while back, I was seeing
what I considered at least to be useful behaviour: basic permission
and sanity checks would be made before returning "100 Continue".

For example, I expect:

  PUT /not-allowed HTTP/1.1
  Host: box
  Content-Length: 5
  Expect: 100-continue

  HTTP/1.1 405 Method Not Allowed
  ...etc...

But with Apache 2.0.48 and mod_dav, I get:

  PUT /not-allowed HTTP/1.1
  Host: box
  Content-Length: 5
  Expect: 100-continue

  HTTP/1.1 100 Continue

  abc
  HTTP/1.1 405 Method Not Allowed
  ...etc..

To me, this seems to defeat the purpose of the continue header, as
specified in RFC 2616:

   The purpose of the 100 (Continue) status (see section 10.1.1) is to
   allow a client that is sending a request message with a request
   body to determine if the origin server is willing to accept the
   request (based on the request headers) before the client sends the
   request body. In some cases, it might either be inappropriate or
   highly inefficient for the client to send the body if the server
   will reject the message without looking at the body.

This is, in fact the case for me.  It is both inappropriate and
inefficient to send the message body if the server is just going to
flat out reject it because it's not in a collection that allows PUT,
for example.  

Is this behaviour of mod_dav intentional?  Is there anything I can
configure to change it?

Thanks!
        
-- 
------------------------------------------------------------------
Brad Spencer - spencer@infointeractive.com - "It's quite nice..."
Systems Architect | InfoInterActive Corp. | A Canadian AOL Company

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org