On Monday 07 August 2017 19:21:52 B.R. via nginx wrote:
> It would be interesting to amend the flawed RFC to adapt to the real world
> then, wouldn't it?
>
> Much like in any languages, specifications/reference and real world offen
> differ, but that should me a pretext to ignor the specs are here
It would be interesting to amend the flawed RFC to adapt to the real world
then, wouldn't it?
Much like in any languages, specifications/reference and real world offen
differ, but that should me a pretext to ignor the specs are here for a
reason: make everyone try to speak the same language and be
On Friday 04 August 2017 09:42:42 Frank Liu wrote:
> 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?
>
[..]
Why sho
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/
*
B.R.
If you read my original post carefully, you will see the test was against
http://nginx.org and I certainly don't have their configuration, but you
can run the same curl test against your own nginx server and get the same
result.
On Fri, Aug 4, 2017 at 3:46 AM, B.R. via nginx wrote:
> How wa
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
How was that 405 generated?
Show used configuration please.
---
*B. R.*
On Fri, Aug 4, 2017 at 7:28 AM, 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
>r
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://
