Forum: NGINX nginx 411 error

Posted by "曾瑞略" <ruilue.zengrl@alibaba-inc.com> (Guest)
on 2013-01-30 06:21
(Received via mailing list)
Hello,

when i change my webserver from apache to tengine,sometimes occurs [411 
Length Required] error.

the request method is post ,but post body is empty.

but when i use apache ,this error never occurs.Is there any solution ?

Thank you!

________________________________

This email (including any attachments) is confidential and may be 
legally privileged. If you received this email in error, please delete 
it immediately and do not copy it or use it for any purpose or disclose 
its contents to any other person. Thank you.

(κθ)ܺлϲܷɱȷռˣɾʼ벻ҪʽиƲκ;͸¶ʼ֮ݡлл
Posted by Maxim Dounin (Guest)
on 2013-01-30 13:38
(Received via mailing list)
Hello!

On Wed, Jan 30, 2013 at 05:20:59AM +0000, 曾瑞略 wrote:

> Hello,
>
> when i change my webserver from apache to tengine,sometimes occurs [411 Length 
Required] error.
>
> the request method is post ,but post body is empty.
>
> but when i use apache ,this error never occurs.Is there any solution ?

The 411 Length Required used to be returned by nginx if client
tried to use chunked Transfer-Encoding.  Support for chunked
Transfer-Encoding was introduced in nginx 1.3.9+, you have to
upgrade to recent nginx 1.3.x if you need it.

--
Maxim Dounin
http://nginx.com/support.html
Posted by Axel (Guest)
on 2013-01-30 13:58
(Received via mailing list)
Hi Maxim,

are you sure that an upgrade to nginx 1.3.x is required?

I had this issue a while ago and I solved it by adding

    chunkin on;
    error_page 411 = @my_411_error;
    location @my_411_error {
       chunkin_resume;
    }

to my vHost configuration.
I never had this error again.

rgds, Axel



Am 30.01.2013 13:37, schrieb Maxim Dounin:
>>
>> but when i use apache ,this error never occurs.Is there any solution
>> ?
>
> The 411 Length Required used to be returned by nginx if client
> tried to use chunked Transfer-Encoding.  Support for chunked
> Transfer-Encoding was introduced in nginx 1.3.9+, you have to
> upgrade to recent nginx 1.3.x if you need it.

--
Never argue with an idiot; people watching may not tell the difference
Posted by Maxim Dounin (Guest)
on 2013-01-30 16:10
(Received via mailing list)
Hello!

On Wed, Jan 30, 2013 at 01:57:27PM +0100, Axel wrote:

>    }
>
> to my vHost configuration.
> I never had this error again.

This uses agentzh chunkin module, which is probably good enough if
you have no other options, but a) not something officially
supported and b) known to have limitations (e.g., AFAIR it doesn't
work with DAV module).

With support for chunked Transfer-Encoding available in 1.3.9+ I
would recommend using nginx 1.3.x instead.

--
Maxim Dounin
http://nginx.com/support.html
Posted by Axel (Guest)
on 2013-01-30 17:16
(Received via mailing list)
Thanks for clarification!

rgds, Axel


Am 30.01.2013 16:09, schrieb Maxim Dounin:
>>    chunkin on;
> supported and b) known to have limitations (e.g., AFAIR it doesn't
> work with DAV module).
>
> With support for chunked Transfer-Encoding available in 1.3.9+ I
> would recommend using nginx 1.3.x instead.

--
Never argue with an idiot; people watching may not tell the difference
Posted by "曾瑞略" <ruilue.zengrl@alibaba-inc.com> (Guest)
on 2013-02-02 03:42
(Received via mailing list)
thanks all ,I will upgrade to nginx 1.3.x.
________________________________________
: nginx-bounces@nginx.org [nginx-bounces@nginx.org]  Axel [ar@xlrs.de]
ʱ: 2013131 0:15
: nginx@nginx.org
: Re: nginx 411 error

Thanks for clarification!

rgds, Axel


Am 30.01.2013 16:09, schrieb Maxim Dounin:
>>    chunkin on;
> supported and b) known to have limitations (e.g., AFAIR it doesn't
> work with DAV module).
>
> With support for chunked Transfer-Encoding available in 1.3.9+ I
> would recommend using nginx 1.3.x instead.

--
Never argue with an idiot; people watching may not tell the difference

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

________________________________

This email (including any attachments) is confidential and may be 
legally privileged. If you received this email in error, please delete 
it immediately and do not copy it or use it for any purpose or disclose 
its contents to any other person. Thank you.

(κθ)ܺлϲܷɱȷռˣɾʼ벻ҪʽиƲκ;͸¶ʼ֮ݡлл
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.