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 2010/11/25 13:11:22 UTC
DO NOT REPLY [Bug 50336] New: PUT failures are not logged
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
Summary: PUT failures are not logged
Product: Apache httpd-2
Version: 2.2.15
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: ne01026@shark.2a.pl
I have set a scratch directory writable by everybody.
drwxr-xr-x 2 wwwrun www 4096 11-24 22:28 /tmp/www
Alias /scratch "/tmp/www"
<Directory /tmp/www>
Allow from all
Order Allow,Deny
</Directory>
I created /tmp/www/test.txt and GET /scratch/test.txt works.
However, the following command does not work:
curl -k -T ./test.html https://server/scratch/
HTTPd returns Error 403, with the following explanation:
The PUT
method is not allowed for the requested URL
So far so good, although not exactly what I wanted.
The request is reported in /var/log/apache2/access_log
BUT
The error is not reported in /var/log/apache2/error_log!
Even after I set LogLevel to debug!
WHY?
Software:
Name : apache2 Relocations: (not relocatable)
Version : 2.2.15 Vendor: openSUSE
Release : 3.7 Build Date: pon, 5 lip 2010,
17:17:44
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures are not logged
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
Christopher Yeleighton <ne...@shark.2a.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #2 from Christopher Yeleighton <ne...@shark.2a.pl> 2010-11-30 08:50:44 EST ---
HTTPd returns Error 403, with the following explanation:
The PUT
method is not allowed for the requested URL
That means the PUT method is recognised but not allowed.
The messsage suggests that it is a policy-related issue.
Otherwise, the error message would be:
The PUT
method is not recognised for the requested URL
BTW, I would like to express my surprise with your supposition that the PUT
method need not be recognised. It is a standard method. E.g. Jigsaw uses this
fact as a justification for not supporting multipart/form-data.
So, if given that you are unwilling to log it as an error for some reason,
please fix the error message at least.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures are not logged
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
William A. Rowe Jr. <wr...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #1 from William A. Rowe Jr. <wr...@apache.org> 2010-11-29 23:26:32 EST ---
Because the core handler rejects unrecognized methods, and you have that data
in the access log, as you note. 403 is an unambiguous response, and there is
nothing more for the core handler to tell you.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures report 403 from core, not 405
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
--- Comment #6 from Christopher Yeleighton <ne...@shark.2a.pl> 2010-11-30 14:05:17 EST ---
(In reply to comment #5)
> FWIW; "Jigsaw uses this fact as a justification for not supporting
> multipart/form-data."
> One has nothing to do with the other, PUT is unrelated to this HTML-ism.
Premises:
1. multipart/form-data exists mainly to permit file upload.
2.
Customers can just PUT their files to Jigsaw, and it is more appropriate for
them to do so according to the HTTP specification.
Conclusion: Jigsaw need not support multipart/form-data.
That was the gist of the argument.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures report 403 from core, not 405
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
--- Comment #7 from Christopher Yeleighton <ne...@shark.2a.pl> 2010-11-30 17:23:05 EST ---
(In reply to comment #5)
> Then I concur, this result code was wrong.
The status code is 405 now, not quite sure what has changed.
(In reply to comment #3)
> METHOD_NOT_ALLOWED reflects the fact that there is no PUT handler distributed
> with httpd, other than mod_dav.
This is a peculiar way of saying things, very misleading.
But that is what the standard says, so I guess it must be like that.
That would invalidate the bug, except for the following detail.
Here are the headers dumped by curl:
HTTP/1.1 100 Continue
HTTP/1.1 405 Method Not Allowed
Date: Tue, 30 Nov 2010 22:14:50 GMT
Server: Apache/2.2.15 (Linux/SUSE)
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
Content-Language: en
Where is Allow:?
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource
identified by the Request-URI. The response MUST include an Allow header
containing a list of valid methods for the requested resource.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures report 403 from core, not 405
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
--- Comment #4 from Christopher Yeleighton <ne...@shark.2a.pl> 2010-11-30 12:09:30 EST ---
(In reply to comment #3)
> METHOD_NOT_ALLOWED reflects the fact that there is no PUT handler distributed
> with httpd, other than mod_dav.
>
> Which raises a question; was mod_dav loaded?
No.
> Enabled?
No.
> Supported by another module or script?
No AFAICT, but HTTPd is complex enough not to be sure.
Thanks for reconsidering.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures report 403 from core, not 405
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
William A. Rowe Jr. <wr...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEW
Summary|PUT failures are not logged |PUT failures report 403
| |from core, not 405
--- Comment #3 from William A. Rowe Jr. <wr...@apache.org> 2010-11-30 11:15:55 EST ---
METHOD_NOT_ALLOWED reflects the fact that there is no PUT handler distributed
with httpd, other than mod_dav.
Which raises a question; was mod_dav loaded? Enabled? Supported by another
module or script?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures do not emit Allow:
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
Christopher Yeleighton <ne...@shark.2a.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|PUT failures report 403 |PUT failures do not emit
|from core, not 405 |Allow:
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 50336] PUT failures report 403 from core, not 405
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50336
--- Comment #5 from William A. Rowe Jr. <wr...@apache.org> 2010-11-30 12:36:47 EST ---
Then I concur, this result code was wrong.
FWIW; "Jigsaw uses this fact as a justification for not supporting
multipart/form-data."
One has nothing to do with the other, PUT is unrelated to this HTML-ism.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org