Welcome! Log In Create A New Profile

Advanced

Re: Unexptected return code

November 09, 2016 05:28AM
‎Makes perfect sense! 


  Original Message  
From: Maxim Dounin
Sent: Wednesday, November 9, 2016 2:02 AM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: Unexptected return code

Hello!

On Tue, Nov 08, 2016 at 11:27:36PM -0800, lists@lazygranch.com wrote:

> I only serve static pages, hence I have this in my conf file:
>
> -----------------------
> ## Only allow these request methods ##
> if ($request_method !~ ^(GET|HEAD)$ ) {
> return 444;
> }
> ----------------
> Shouldn't the return code be 444 instead of 400?
> ----------------------------------------
> 400 111.91.67.118 - - [09/Nov/2016:05:18:38 +0000] "CONNECT search.yahoo.com:443 HTTP/1.1" 173 "-" "-" "-"
> -------------------------------
>
> This is more of a curiosity rather than an issue.

There is no support for CONNECT method in nginx. As a result,
CONNECT requests are rejected as invalid while parsing a request
line (as there is no URI nginx expects to see).

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Unexptected return code

gariac November 09, 2016 02:28AM

Re: Unexptected return code

Maxim Dounin November 09, 2016 05:04AM

Re: Unexptected return code

gariac November 09, 2016 05:28AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 77
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready