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 registration information for text/xml is in all respects the same
as that given for application/xml above ([Section 9.1](https://www.rfc-editor.org/rfc/rfc7303#section-9.1)), except that
the "Type name" is "text".
So the RFC registers application/xml is the "main" mime type and text/xml is an alias.
But in real-life usage, text/xml seems preferred: linux file utility and go stdlib http.DetectContentType don't have mime aliases, and they both exclusively use text/xml. OTOH, apache tika does it the other way around 😕
mimetype exclusively used text/xml until now, so adding application/xml as an alias seems appropriate.
According to RFC7303, text/xml is an alias to application/xml. But
considering we we're using text/xml as the main mime type until now,
changing to main=application/xml alias=text/xml would cause trouble to
users. So for now, we're keeping as: main=text/xml alias=application/xml
https://www.rfc-editor.org/rfc/rfc7303
The text was updated successfully, but these errors were encountered: