www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: mod_mime/326: rfc2068 non-adherance (section 10.4.6 405 Method Not Allowed)
Date Tue, 08 Apr 1997 10:00:02 GMT
The following reply was made to PR mod_mime/326; it has been noted by GNATS.

From: Dean Gaudet <dgaudet@arctic.org>
To: Gavin Vess <gavin@onlinefocus.com>
Subject: Re: mod_mime/326: rfc2068 non-adherance (section 10.4.6  405 Method Not Allowed)
Date: Tue, 8 Apr 1997 02:53:11 -0700 (PDT)

 
 Try doing it with:
 
 POST /foobar HTTP/1.0
 
 You did not include the HTTP/1.0 so the server assumes HTTP/0.9 which of
 course has no headers in the output.  I tried against 1.2b8 and it had no
 problem issuing an Allow header. 
 
 Thanks for the compliments.
 
 Dean
 
 On Tue, 8 Apr 1997, Gavin Vess wrote:
 
 > 
 > >Number:         326
 > >Category:       mod_mime
 > >Synopsis:       rfc2068 non-adherance (section 10.4.6  405 Method Not Allowed)
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    apache (Apache HTTP Project)
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   apache
 > >Arrival-Date:   Tue Apr  8 00:00:02 1997
 > >Originator:     gavin@onlinefocus.com
 > >Organization:
 > apache
 > >Release:        1.2b7
 > >Environment:
 > Solaris, gcc 2.7.2, 1.2b7, etc.
 > 
 > % diff Configuration Configuration.tmpl
 > 169c169
 > < Module status_module       mod_status.o
 > ---
 > > # Module status_module             mod_status.o
 > 174c174
 > < Module info_module         mod_info.o
 > ---
 > > # Module info_module         mod_info.o
 > 181c181
 > < Module anon_auth_module    mod_auth_anon.o
 > ---
 > > # Module anon_auth_module    mod_auth_anon.o
 > 189c189
 > < Module dbm_auth_module     mod_auth_dbm.o
 > ---
 > > # Module dbm_auth_module     mod_auth_dbm.o
 > 205c205
 > < Module digest_module       mod_digest.o
 > ---
 > > # Module digest_module       mod_digest.o
 > 230c230
 > < Module usertrack_module      mod_usertrack.o
 > ---
 > > # Module usertrack_module      mod_usertrack.o
 > >Description:
 > Excerpt from rfc2068 (http://www.w3.org/pub/WWW/Protocols/rfc2068/rfc2068):
 > 
 > 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.
 > 
 > -
 > %telnet a_box_running_apache_1_2b7 80
 > Trying 170.1.195.50...
 > Connected to timecard.onlinefocus.com.
 > Escape character is '^]'.
 > POST http://timecard.onlinefocus.com/tcgi/tlogin
 > <HTML><HEAD>
 > <TITLE>405 Method Not Allowed</TITLE>
 > </HEAD><BODY>
 > <H1>Method Not Allowed</H1>
 > The requested method POST is not allowed for the URL /tcgi/tlogin.<P>
 > </BODY></HTML>
 > Connection closed by foreign host.
 > -
 > 
 > 
 > I'd just like to say that I'm quite impressed with the quality
 > of Apache and am interested in seeing it continue to prosper.
 > 
 > 
 > -- 
 > Cheers,
 > Gavin Vess
 > 
 > OnlineFocus
 > 408/725-7352
 > gavin@onlinefocus.com
 > >How-To-Repeat:
 > Set the ACTION of any FORM to any object which does not recognize POST methods.
 > Submit form.  I'd expect any attempt to use a POST method with an object which
 > does not recognize the POST method will not return a list of ALLOWable methods.
 > >Fix:
 > Oh, if I only had the time to examine the module's code .
 > >Audit-Trail:
 > >Unformatted:
 > 
 > 
 > 
 

Mime
View raw message