Web-app manifest fails to load behind an authenticating proxy

Open Beginner friendly
  • Is something wrong?
#96 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
html
Domain
frontend

Research direction

Find the template that renders the web-app manifest link and check its existing rel="manifest" element. Add the suggested crossorigin="use-credentials" attribute, then verify the rendered link includes it. Done means the manifest request can send the session cookie behind an authenticating proxy.

Written by the indexing model from the issue text.

Description

Summary

Browsers fetch <link rel="manifest"> without credentials. Behind an SSO proxy (Cloudflare Access in our case), that request is redirected to the login page and fails with a CORS error in the console. Nothing breaks, but it's noise in every page load and in security reviews.

Suggested fix

Add crossorigin="use-credentials" to the manifest link, so the session cookie is sent with it:

<link rel="manifest" href="{% static 'manifest.json' %}" crossorigin="use-credentials">
Dominant language
HTML
Stars
6
Forks
4
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from brainthee/CHAOTICA

All issues in brainthee/CHAOTICA

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.