Type: Bug Report
git --no-pager taggit --no-pager log -1a7a849e7bf6f80857d727d31f1ef9200998bc54f
node --versionnpm --versionUsed provided Dockerfile, so node:10.1-alpine
name and versionManifest JSON is not fetched with credentials
When the request is sent out for manifest.json the cookies the browser normally uses should be attached to the request.
No cookies are attached to the request.
Javascript fetchers have options to attach cookies and credentials to request. Enable it for manifest.json.
document.cookie = "testcookie=hello"; in the developer console.:authority: x
:method: GET
:path: /api/client/settings
:scheme: https
accept: application/json, text/plain, */*
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9,sv;q=0.8
cookie: testcookie=hello
dnt: 1
referer: https://x/overview
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
:authority: x
:method: GET
:path: /manifest.json
:scheme: https
accept: */*
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9,sv;q=0.8
dnt: 1
referer: https://x/overview
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
The authentication proxy I'm using in front of flood sets cookies to allow access to resources. Since manifest.json is not fetched with the cookies, it will reject the request and the flood interface fails to load.
@bluecmd Hi, can you finish to fill the template please (Your Environment).
Hi, I already did:
Environment name and version:
[...]
Used provided Dockerfile, so node:10.1-alpine
@bluecmd I didn't see you were using the docker
Most helpful comment
@bluecmd I didn't see you were using the docker