You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consequences of a server ignoring representation metadata are not clear to me.
Is this related to the fact that they are associated with the upload resource?
OTOH, Content-Type and Content-Encoding are associated with the target resource.
Server MAY interpret this metadata or MAY ignore it.
IIRC, the statement about ignoring metadata was originally intended for Content-Disposition. Clients can set this header to indicate a filename, but servers are not required to respect or process it.
But the statement doesn't add much value to the draft, so we can probably get rid of "Servers MAY interpret this metadata or MAY ignore it". Thanks for bringing this up!
Question
The consequences of a server ignoring representation metadata are not clear to me.
Is this related to the fact that they are associated with the upload resource?
OTOH, Content-Type and Content-Encoding are associated with the target resource.
https://github.com/httpwg/http-extensions/blame/9ecc41277598ece1ab372b9f8c141b1838783e56/draft-ietf-httpbis-resumable-upload.md#L276
Then, we have:
The text was updated successfully, but these errors were encountered: