Segfault in nginx 1.0.5

Sven 'Darkman' Michels sven at
Mon Aug 8 07:41:11 UTC 2011


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...).


More information about the nginx mailing list