Fix frontend api request block due to mixed content #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now TO staging fails to fetch data from API because the API request is blocked by the browser. After digging into what's going on, I found that frontend tries to request artefacts through the following url
https://test-observer-api-staging.canonical.com/v1/artefacts?family=snap
. The api then responds with a 307 redirect tohttp://test-observer-api-staging.canonical.com/v1/artefacts/?family=snap
because fastapi redirects request to match trailing slash of endpoint. But the issue is that the redirect switches from https scheme to http. The browser detects this and blocks the request.Note that this problem doesn't exist on local development because local development doesn't use a tls certificate. So all requests are http. Hence there is no mixed content shenanigans.