Welcome! Log In Create A New Profile

Advanced

Re: Segfault in nginx 1.0.5

Maxim Dounin
August 08, 2011 05:14AM
Hello!

On Mon, Aug 08, 2011 at 09:41:11AM +0200, Sven 'Darkman' Michels wrote:

> Hi,
>
> Am 08.08.2011 08:48, schrieb Maxim Dounin:
> > This problem is specific to error_page 400, as 400 means "bad
> > request" and request may not have some required parts set (due to
> > being actually bad).
>
> but in this case an error or warning or whatsoever would be better
> than just a segfault, right? ;)
>
> Don't want to bug at it, i just think that catching such config
> problems would be good for the future (and as i'm not a coder
> in general, i cannot fix it by myself...).

I specifically outlined in my original reply that this *is* a bug
(and it obviously needs fixing).

Maxim Dounin

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

Segfault in nginx 1.0.5

Kingsley Foreman August 07, 2011 09:52PM

Re: Segfault in nginx 1.0.5

John Macleod August 07, 2011 10:32PM

Re: Segfault in nginx 1.0.5

Maxim Dounin August 08, 2011 02:42AM

RE: Segfault in nginx 1.0.5

Kingsley Foreman August 08, 2011 02:44AM

RE: Segfault in nginx 1.0.5

Kingsley Foreman August 08, 2011 02:48AM

Re: Segfault in nginx 1.0.5

Maxim Dounin August 08, 2011 02:50AM

RE: Segfault in nginx 1.0.5

Kingsley Foreman August 08, 2011 02:50AM

Re: Segfault in nginx 1.0.5

Sven 'Darkman' Michels August 08, 2011 03:42AM

Re: Segfault in nginx 1.0.5

Maxim Dounin August 08, 2011 05:14AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 158
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