How was that 405 generated? Show used configuration please. --- *B. R.* On Fri, Aug 4, 2017 at 7:28 AM, Frank Liu <[email protected]> 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? > > curl -v -X TRACE http://nginx.org > * Rebuilt URL to: http://nginx.org/ > * Trying 95.211.80.227... > * TCP_NODELAY set > * Connected to nginx.org (95.211.80.227) port 80 (#0) > > TRACE / HTTP/1.1 > > Host: nginx.org > > User-Agent: curl/7.54.0 > > Accept: */* > > > < HTTP/1.1 405 Not Allowed > < Server: nginx/1.13.3 > < Date: Fri, 04 Aug 2017 05:25:26 GMT > < Content-Type: text/html; charset=utf-8 > < Content-Length: 173 > < Connection: close > < > <html> > <head><title>405 Not Allowed</title></head> > <body bgcolor="white"> > <center><h1>405 Not Allowed</h1></center> > <hr><center>nginx/1.13.3</center> > </body> > </html> > * Closing connection 0 > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
