Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If the HTTP Method is not all upper-case, Nginx rejects the request and sends a 400 response along with its internal 400 HTML error page.
no details shown on “error_log info”
example: Link, LInK, SeaRCH, VeRB, etc … upper-case versions of those work, its jut the mixed case.
From the HTTP 1.1 RFC;
As far as I can tell, Nginx is doing the right thing according to the specification. If you disagree, you’ll have to explain what you think it’s doing wrong more clearly.
Edit: Yes, I agree with the answer from @JulianReschke, it should return a 501 status code, not a 400, good catch.