jinql
/
ngx-fancyindex
mirror of https://github.com/aperezdc/ngx-fancyindex
1
0
Fork 0
Code Issues Releases Wiki Activity

Fixed the wrong status code check when including header/footer in NGinx 1.1.16 

where ngx_http_subrequests returns NGX_OK (0) and not NGX_HTTP_OK (200) on a
successful completion of the subrequest.
pull/4/head
Stefan Rubner 2012-03-08 23:49:32 +01:00
parent 607159a61d
commit 07614d5abe
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ngx_http_fancyindex_module.c
View File

@ -803,8 +803,8 @@ ngx_http_fancyindex_handler(ngx_http_request_t *r)
ngx_log_debug1(NGX_LOG_DEBUG_HTTP, r->connection->log, 0, ngx_log_debug1(NGX_LOG_DEBUG_HTTP, r->connection->log, 0,
"http fancyindex: header subrequest status = %i", "http fancyindex: header subrequest status = %i",
sr->headers_out.status); sr->headers_out.status);
/* ngx_http_subrequest in 1.1.16 returns NGX_OK(0), not NGX_HTTP_OK(200) */
if (sr->headers_out.status != NGX_HTTP_OK) { if (sr->headers_out.status != NGX_OK) {
/* /*
* XXX: Should we write a message to the error log just in case * XXX: Should we write a message to the error log just in case
* we get something different from a 404? * we get something different from a 404?
@ -881,6 +881,7 @@ add_builtin_header:
"http fancyindex: header subrequest status = %i", "http fancyindex: header subrequest status = %i",
sr->headers_out.status); sr->headers_out.status);
/* see above: ngx_http_subrequest in 1.1.16 resturns NGX_OK (0) not NGX_HTTP_OK (200) */
if (sr->headers_out.status != NGX_HTTP_OK) { if (sr->headers_out.status != NGX_HTTP_OK) {
/* /*
* XXX: Should we write a message to the error log just in case * XXX: Should we write a message to the error log just in case