You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2006/04/17 16:29:42 UTC

DO NOT REPLY [Bug 39323] - "If GET is used it will also restrict HEAD requests."

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39323>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39323


wrowe@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From wrowe@apache.org  2006-04-17 14:29 -------
RFC 2616 is absolutely clear on this point, a HEAD request mirrors the 
corresponding GET request.  The client must not have to put up with any
other behavior for the server, so your request will not be considered.

Exploring further...

"For my webDAV-httpd instance, I want to allow to many users to upload files
and see the contents of the directory, where the files are uploaded."

Seeing the content of the directory has nothing to do with HEAD v.s. GET
permissions.  It's the distinction between resources /foo/ (the directory
container) and /foo/.+ (entities within the directory).  Please consult the
appropriate user forum for peer-to-peer support on how to configure exactly
what you are attempting to accomplish.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org