[MAGNOLIA-7224] Link Manifest results to a 401 error Created: 18/Dec/17 Updated: 18/Dec/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | Virtual URI mappings |
| Affects Version/s: | 5.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Cédric Eberhardt | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
Hi. It was a bit different than expected on the previous comment sorry. So, this is the current bug. Loading the web app manifest with `<link rel="manifest" href="..">` results to a 401 error if the anonymous user doesn't have the get access event if you are logged in with the superuser. Opening a new tab on the browser and navigating to this file works fine. If I try with `rel="stylesheet"`, it's technically wrong but it works fine again. I get a 200 response code as expected. |