MSC4138: Update allowed HTTP methods in CORS responses

[turt2live]

Rendered

In line with https://github.com/matrix-org/matrix-spec/issues/1700, the following disclosure applies:

I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published with my role as a member of the SCT.

Related: https://github.com/matrix-org/matrix-js-sdk/pull/4188

FCP tickyboxes

[clokep]

Seems quite reasonable!

@mscbot fcp merge

[mscbot]

Team member @clokep has proposed to merge this. The next step is review by the rest of the tagged people:

• [x] @clokep
• [ ] @dbkr
• [ ] @uhoreg
• [x] @turt2live
• [x] @ara4n
• [x] @anoadragon453
• [x] @richvdh
• [x] @tulir
• [x] @erikjohnston
• [x] @KitsuneRal

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.

[ara4n]

it feels weird to be allowing methods without matching MSCs that demand them, but not enough to block it.

[mscbot]

:bell: This is now entering its final comment period, as per the review above. :bell:

[mscbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

[turt2live]

updated by https://github.com/matrix-org/matrix-spec-proposals/pull/4187