7 messages in ru.sysoev.nginxRe: bug report: SSI -> signal 10 (ngi...
FromSent OnAttachments
Hannes HaugNov 4, 2008 11:21 am 
Maxim DouninNov 4, 2008 2:41 pm 
Hannes HaugNov 5, 2008 11:01 pm 
Maxim DouninNov 6, 2008 2:49 am 
Igor SysoevNov 6, 2008 2:50 am 
Maxim DouninNov 6, 2008 3:17 am 
Igor SysoevNov 6, 2008 4:55 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: bug report: SSI -> signal 10 (nginx 0.7.10, Solaris 10)Actions...
From:Igor Sysoev (is@rambler-co.ru)
Date:Nov 6, 2008 2:50:59 am
List:ru.sysoev.nginx

On Thu, Nov 06, 2008 at 01:50:22PM +0300, Maxim Dounin wrote:

Hello!

On Thu, Nov 06, 2008 at 08:01:58AM +0100, Hannes Haug wrote:

Yes Maxim,

your patch fixes the problem.

Thanks for testing.

But there remains an issue: Errors on subrequests (e.g. 404) result in the inclusion of the error pages in the main page. I.e. in the body of the main page there starts a new html document with the error message.

It's by design. Subrequests are just included into main page as is, regardless of the error code. If you don't want error replies to be included you have to write in your config something like this:

location /include/ { error_page 404 /empty;

- error_page 404 /empty; + error_page 404 = /empty;

} location = /empty { return 204; }

So if you use <!--#include virtual="/include/file" --> and there is no "/include/file" - nginx will return empty page instead, and no output will appear in main document.

See http://wiki.codemongers.com/NginxHttpCoreModule#error_page for details.

Maxim Dounin

-- Igor Sysoev http://sysoev.ru/en/