Library routes response provides bad Content-Type header (#1026) · Issues · funkwhale / funkwhale

Library routes response provides bad Content-Type header

Steps to reproduce

Visit a library url, example: https://funkwhale.eliotberriot.com/federation/music/libraries/c400c8b2-3c62-41ec-bb89-4c3922fcfadb
Check response header

What happens?

Content-Type is text/html

What is expected?

Content-Type is application/activity+json

Context

Sharing a library url

Funkwhale version(s) affected: Version 0.20.1+git.f8675c60

<!--
Hi there! You are reporting a bug on this project, and we want to thank you!

If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.

To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.

Please do not edit the following line, it's used for automatic classification
-->

## Steps to reproduce

1. Visit a library url, example: https://funkwhale.eliotberriot.com/federation/music/libraries/c400c8b2-3c62-41ec-bb89-4c3922fcfadb
2. Check response header

## What happens?

Content-Type is `text/html`

## What is expected?

Content-Type is `application/activity+json`

## Context

Sharing a library url

**Funkwhale version(s) affected**: Version 0.20.1+git.f8675c60

<!--
If relevant, share additional context here like:

- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->

Edited Feb 19, 2020 by Agate

Discussion
Designs

The one place for your designs

To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.