The GET call to retrieve images when attempting to view monster pages for several monsters are failing with 400 errors when I use Chrome. The response from the backend is suggesting there is an issue with the request's header's size. Weird thing is that FireFox seems to pull the same urls up with with no issues. Below are just two examples.
No change unfortunately. Chrome is usually pretty good about managing cached content, but even after clearing it out manually then shutting down and restarting the Chrome application the images still won't load.
The GET call to retrieve images when attempting to view monster pages for several monsters are failing with 400 errors when I use Chrome. The response from the backend is suggesting there is an issue with the request's header's size. Weird thing is that FireFox seems to pull the same urls up with with no issues. Below are just two examples.
Receiving almost the identical error 4 years later. It even works in incognito mode - but not in basic Chrome with no extensions. WTH?
This XML file does not appear to have any style information associated with it. The document tree is shown below. <Error> <Code>RequestHeaderSectionTooLarge</Code> <Message>Your request header section exceeds the maximum allowed size.</Message> <MaxSizeAllowed>8192</MaxSizeAllowed> <RequestId>F7WT3DNAZB2P89T4</RequestId> <HostId>6YFQQeT0fJEXNDE2O9qXrZfrZ2eQ1T3UQVBg7JyowuaEtUeU9Jr1sNUxHqdHILUSxkXI5MDTHDc=</HostId> </Error>
In my case I switched to a different browser and everything loaded just fine - which shot several of my theories down. If you don't need any plugins try switching to Firefox and see if that helps.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The GET call to retrieve images when attempting to view monster pages for several monsters are failing with 400 errors when I use Chrome. The response from the backend is suggesting there is an issue with the request's header's size. Weird thing is that FireFox seems to pull the same urls up with with no issues. Below are just two examples.
Page:
https://www.dndbeyond.com/monsters/2560775-dhergoloth
Request:
Page:
https://www.dndbeyond.com/monsters/17135-drow-mage
Request Method: GET
Status Code: 400
Clear your cookies and cache and history.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
No change unfortunately. Chrome is usually pretty good about managing cached content, but even after clearing it out manually then shutting down and restarting the Chrome application the images still won't load.
Receiving almost the identical error 4 years later. It even works in incognito mode - but not in basic Chrome with no extensions. WTH?
In my case I switched to a different browser and everything loaded just fine - which shot several of my theories down. If you don't need any plugins try switching to Firefox and see if that helps.