When adding an ETag to an HTTP response, should I include the media type?

Question

0

Asked: May 26, 20262026-05-26T14:10:32+00:00 2026-05-26T14:10:32+00:00

When adding an ETag to an HTTP response, should I include the media type?

0

When adding an ETag to an HTTP response, should I include the media type? Of course, I understand that the ETag is opaque, but here is an example:

Say I have a client that requests a Person in application/json. I look it up and create my ETag and send back the JSON representation of the person
Now the same client makes another request for the same person (which has not been modified) at the same URI but wants it in application/xml.

Clearly it is incorrect to simply return a 304, but my question is, in the second request, would I expect the ETags to match but no cache based on the Accept header (or the content header). Also, is it even possible that the cache will have two representations from the same URI, or would you always have an invalid cache every time your Content-Type switched?