This thread was archived. Please ask a new question if you need help.
400 Bad Request Request Header Or Cookie Too Large nginx
I have used Firefox for many years. I frequently have many tabs open. I have recently begun to have this problem: I open a site that uses a CDN for images, and the images will not load, and I get the error message in the title for the images.
Creating a new profile sometimes fixes it. Getting rid of cookies sometimes fixes it. but changing to a new profile is time consuming and inconvenient. Why am I suddenly having this problem?
This is the page where the problem occurs: https://www.star.nesdis.noaa.gov/goes/conus_band.php?sat=G16&band=GEOCOLOR&length=12
and the images are addressed like this: https://cdn.star.nesdis.noaa.gov/GOES16/ABI/CONUS/GEOCOLOR/20200501541_GOES16-ABI-CONUS-GEOCOLOR-2500x1500.jpg
I just now cleared my cache, deleted nearly all cookies manually, restarted FireFox, and can't view these images.
Here is my system info: OS: Windows 10 Browser: Firefox 73 (73.0) Mobile: false Cookies: true Screen Size: 1680 x 1050 Full User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
This is a very recent problem, cropping up constantly since last week. Is it caused by a recent update?
All Replies (5)
Hi lori.brown, where does that message show up?
Do you use any settings or add-ons that modify the headers? For example, in addition to changes to cookies returned to the site, headers could be modified by preferences or extensions directed toward reducing or masking referring site information.
Is this the only CDN your Firefox has trouble with? Some users have problems with numerous URLs that contain cdn in the server name, perhaps due to security or parental control filters.
The message shows up if I go directly to view the image via the url I showed you. When I view a page that should be loading the images, they just don't appear. Investigating your other question w/ systems folks.
Screen capture of message and image URL that produces it.
If clearing cookies didn't help then it is possible that the cookies.sqlite file in the Firefox profile folder that stores the cookies got corrupted.
- rename/remove cookies.sqlite (cookies.sqlite.old) and when present delete cookies.sqlite-shm and cookies.sqlite-wal in the Firefox profile folder with Firefox closed in case cookies.sqlite got corrupted.
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Folder/Directory:
Windows: Open Folder; Linux: Open Directory; Mac: Show in Finder
We have identified a cookie that is implicated in this, and it is from our parent organization. We are enlarging the permissible cookie size in NGINX, but will keep these other suggestions at ready. Thank you so much for your assistance.