That would depend on what kind of service you're implementing. "HTTP/1.1 does not define how a PUT method affects the state of an origin server." I don't thin

That would depend on what kind of service you're implementing. "HTTP/1.1 does not define how a PUT method affects the state of an origin server." I don't think it was ever the design or intent of PUT to store the exact representation that you gave it, and I would be surprised to see evidence otherwise. Conceptually it's no different from POSTing (or PUTting) application/json to produce a resource that will be represented as text/html. How do you convert JSON to HTML? Depends on the service.