-
Notifications
You must be signed in to change notification settings - Fork 70
Open
Description
How should upgrade-insecure-requests: 1
be handled when encountered in the response header?
{
host: 'localhost:8443',
'user-agent': 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0',
accept: 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8',
'accept-language': 'en-US,en;q=0.5',
'accept-encoding': 'gzip, deflate, br',
authorization: 'Digest username="admin", realm="Users", nonce="54d33865...", uri="/Big_Buck_Bunny_360_10s_5MB.mp4", algorithm=MD5, response="1ed75a58...", qop=auth, nc=00000007, cnonce="5e6299d2..."',
connection: 'keep-alive',
'upgrade-insecure-requests': '1', // <-------------- HERE
'sec-fetch-dest': 'document',
'sec-fetch-mode': 'navigate',
'sec-fetch-site': 'none',
'sec-fetch-user': '?1'
}
When I receive this header, there is no sendStatus()
function on the http response
argument.
Metadata
Metadata
Assignees
Labels
No labels