Why does NGinx send content in a HTTP 304 response when If-None-Match / If-Modified-Since is a match?

My default NGinx installation is returning a 304 Not Modified response to a request which has a matching If-None-Match header and a non-expired If-Modified-Since header which is correct behaviour but NGinx also adds the content of the resource to the 304 response. One would think that NGinx wouldn't add the content, but simply return the 304 with an empty body indicating to the browser that using their cached resource is sufficient.

Is there a reason for this behaviour and how do I disable it?

Replay

Category: nginx Time: 2016-07-28 Views: 0

Related post

iOS development

Android development

Python development

JAVA development

Development language

PHP development

Ruby development

search

Front-end development

Database

development tools

Open Platform

Javascript development

.NET development

cloud computing

server

Copyright (C) avrocks.com, All Rights Reserved.

processed in 0.163 (s). 12 q(s)