Allow cross-origin requests to /.well-known/* URLs. (#9083)
Right now, this includes three endpoints: host-meta, webfinger, and change-password. host-meta and webfinger are publicly available and do not use any authentication. Nothing bad can be done by accessing them in a user's browser. change-password being CORS-enabled will only reveal the URL it redirects to (which is /auth/edit) but not anything about the actual /auth/edit page, because it does not have CORS enabled. The documentation for hosting an instance on a different domain should also be updated to point out that Access-Control-Allow-Origin: * should be set at a minimum for the /.well-known/host-meta redirect to allow browser-based non-proxied instance discovery.
This commit is contained in:
parent
4ea718ef18
commit
13e049d772
|
@ -9,6 +9,10 @@ Rails.application.config.middleware.insert_before 0, Rack::Cors do
|
||||||
allow do
|
allow do
|
||||||
origins '*'
|
origins '*'
|
||||||
|
|
||||||
|
resource '/.well-known/*',
|
||||||
|
headers: :any,
|
||||||
|
methods: [:get],
|
||||||
|
credentials: false
|
||||||
resource '/@:username',
|
resource '/@:username',
|
||||||
headers: :any,
|
headers: :any,
|
||||||
methods: [:get],
|
methods: [:get],
|
||||||
|
|
Loading…
Reference in New Issue