304 handling for non-spdy requests is exactly same as that of 204 handling
(Reference : ngx_http_header_filter_module.c::ngx_http_header_filter()).
SPDY requests too should be handled same way.
Handle 204/304 response for SPDY requests in same way as the same way that
are handled for non-SPDY requests
---
.../src/http/ngx_http_spdy_filter_module.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
a/service/proxy/nginx-1.6.2/src/http/ngx_http_spdy_filter_module.c
b/service/proxy/nginx-1.6.2/src/http/ngx_http_spdy_filter_module.c
index a31ad1f..8f975f5 100644
--- a/service/proxy/nginx-1.6.2/src/http/ngx_http_spdy_filter_module.c
+++ b/service/proxy/nginx-1.6.2/src/http/ngx_http_spdy_filter_module.c
@@ -147,10 +147,10 @@ ngx_http_spdy_header_filter(ngx_http_request_t *r)
break;
case NGX_HTTP_NOT_MODIFIED:
- r->header_only = 1;
- break;
-
case NGX_HTTP_NO_CONTENT:
+ /* take same action for "NGX_HTTP_NOT_MODIFIED" as that for
+ "NGX_HTTP_NO_CONTENT" */
r->header_only = 1;
ngx_str_null(&r->headers_out.content_type);
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
