httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@decus.org (Rodent of Unusual Size)
Subject Re: protocol/378: Wrong behavior on an OPTIONS request
Date Wed, 23 Apr 1997 15:25:32 GMT
    Is this a legitimate issue?  Roy?  If so, it's another one for the
    "HTTP/1.1 non-compliance" page.  This would make two, correct?  This
    and the proxy?

    #ken    :-)}

>From the fingers of Eilebrecht, Lars <sfx@unix-ag.org> flowed the following:
>
>>Number:         378
>>Category:       protocol
>>Synopsis:       Wrong behavior on an OPTIONS request
>>Arrival-Date:   Sun Apr 13 13:10:02 1997
>>Release:        1.2b7
>>Description:
>  I'm wondering if the OPTIONS method of Apache is really
>  conforming to RFC2068...
>  Example:
>    PUT is configured via 'Script PUT /cgi-bin/put.cgi' and
>    the servers allows PUT to its documents (<Limit PUT>).
>    When I try the request "OPTIONS /cgi-bin/put.cgi" the reponse
>    contains "PUT" in the Allow-Header, but I cannot PUT to
>    *this* resource.
>    When I try a request like "OPTIONS /put_allowed_dir/index.html"
>    the response does not contain "PUT" as allowed, although I
>    can PUT something to this location.
>    When I try OPTIONS on a resource that is protected via some
>    means of authentication the response contains an authentication
>    challenge, although RFC2068 says that there should be no initiation

Mime
View raw message