A restrictive GET or HEAD demand has been gotten and would have brought about a 200 OK reaction on the off chance that it were not for the way that the condition assessed to bogus.
At the end of the day, there is no requirement for the server to move a representation of the objective asset in light of the fact that the request shows that the customer, which made the request contingent, as of now has a legitimate representation; the server is in this way diverting the customer to utilize that put away representation as though it were the payload of a 200 OK reaction.
The server creating a 304 reaction MUST produce any of the accompanying header handle that would have been sent in a 200 OK reaction to a similar request: Cache-Control, Content-Location, Date, ETag, Expires, and Vary.
Since the objective of a 304 reaction is to limit data move when the beneficiary as of now has at least one stored representations, a sender SHOULD NOT produce representation metadata other than the above recorded fields except if said metadata exists to control reserve refreshes (e.g., Last-Modified may be valuable if the reaction doesn’t have an ETag field).
Necessities on a store that gets a 304 reaction are characterized in Section 4.3.4 of RFC7234. On the off chance that the restrictive request began with an outbound customer, for example, a client operator with its own reserve sending a contingent GET to a mutual intermediary, at that point the intermediary SHOULD advance the 304 reaction to that customer.
A 304 reaction can’t contain a message-body; it is constantly ended by the principal void line after the header fields.