-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSC2701: Clarifying Content-Type
usage in the media repo
#2701
Conversation
Content-Type
usage in the media repo
@turt2live: Given that this seems to be largely a statement of the status quo, why is it |
this looks ready to go to me, and I think we should FCP it. |
Largely because of the criteria when applying that label: Nothing in the PR description to say that it needs an implementation. This translates to it being on my todo list to figure out the status of it. |
I assert that it already has an implementation, and I propose FCP. @mscbot fcp merge. |
Unknown disposition 'merge.'. |
ohh wait, I seem to have jumped the gun here. Sorry! |
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
I've updated this to match current behaviour, which also means no specific implementation is required. Sending it off for review: @mscbot fcp merge |
Team member @turt2live has proposed to merge this. The next step is review by the rest of the tagged people: Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for information about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
* Proposal to clarify how Content-Type works with media * Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> * Modernize wording --------- Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Spec PR: matrix-org/matrix-spec#1758 |
For `GET /download`, the server MUST return a `Content-Type` which is either exactly the same as the | ||
original upload, or reasonably close. The bounds of "reasonable" are: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that this MSC was merged a while ago, but would it have made sense to also mandate a X-Content-Type-Options nosniff
header as part of the response?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kladki Could you open this question as a new issue on https://github.com/matrix-org/matrix-spec/issues? Then we can discuss and track it.
Spec PR: matrix-org/matrix-spec#1935 |
Merged 🎉 |
Rendered
Implementations: None required - see "Unstable Prefix" section for details.
FCP tickyboxes