HTTP/405

Fri Aug 4 16:42:42 UTC 2017

Valentin,

I checked the trac and basically it says very complicated to properly
implement. When I try the same curl against apache.org, they just return a
blank Allow header to compliant RFC. Maybe nginx can do the same?

curl -v -X TRACE http://apache.org

* Rebuilt URL to: http://apache.org/

*   Trying 140.211.11.105...

* TCP_NODELAY set

* Connected to apache.org (140.211.11.105) port 80 (#0)

> TRACE / HTTP/1.1

> Host: apache.org

> User-Agent: curl/7.54.0

> Accept: */*

>

< HTTP/1.1 405 Method Not Allowed

< Date: Fri, 04 Aug 2017 16:38:42 GMT

< Server: Apache/2.4.7 (Ubuntu)

< Allow:

< Content-Length: 223

< Content-Type: text/html; charset=iso-8859-1

<

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html><head>

<title>405 Method Not Allowed</title>

</head><body>

<h1>Method Not Allowed</h1>

<p>The requested method TRACE is not allowed for the URL /.</p>

</body></html>

* Connection #0 to host apache.org left intact

On Fri, Aug 4, 2017 at 4:05 AM, Valentin V. Bartenev <vbart at nginx.com>
wrote:

> On Thursday 03 August 2017 22:28:41 Frank Liu wrote:
> > https://tools.ietf.org/html/rfc7231#page-59 says:
> >
> > ... The origin server MUST generate an
> >    Allow header field in a 405 response containing a list of the target
> >    resource's currently supported methods.
> >
> > nginx doesn't seem to have Allow header field. Is that against RFC?
> >
>
> Please, look at the explanations in https://trac.nginx.org/nginx/
> ticket/1161
>
>   wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170804/5f2db11c/attachment-0001.html>