WebFinger endpoint responds with XRD instead of JRD in browser
Environment
- Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.6.51-650-g0b9bc4a0-develop as observed on lain.com
Bug description
Actual behavior:
- WebFinger when requested in a browser is responding with an XRD that gets downloaded -- likely because browsers by default specify an Accept header that includes application/xml
Expected behavior:
- WebFinger responds with a JRD in-browser -- this is the expected response of the .well-known/webfinger endpoint and also the response that pretty much every other implementation seems to express
In searching I found #2579 (closed) which may or may not be related.