7 Replies

The issue with this error is I don’t yet know if I’ll be able to fix it or not. It depends on whether the bad request originates with something I can control or not. I can’t control everything your phone browser sends in a request. If the thing causing the error is something I told your phone to send, then I can fix it, but otherwise, I might not be able to. I get this same error on random sites at times and have also had to clear my cookies to fix it.

There’s a chance I might be able to increase the allowed header size to fix it, but it depends how big the header is. It’s correct to not accept enormous ones

If anyone is able to, it would be good to know what pages it’s happening on, like what link you clicked on when it happened. Just in case there was something wrong in the URL, but I doubt it if clearing cookies fixed it.

@Crumpet: alright! Thank you for the advice! The problem usually comes up on the website itself. Sometimes I can open one page, but as I click to go to another the error message comes up. I will definitely try your advice though, thank you!

Can you confirm if your error message was a bad request one, themultifandomloser? And if so, did it happen on the site or in the pattern maker?

That error is probably actually not a code issue. It will be something with the cookie or server configuration. I noticed that one of my old patterns wasn’t loading properly earlier, but I didn’t get an error. It was just slow and then the page styles didn’t load.

Try clearing your cookies and see if that helps, trickster. It might not if the cookie goes right back to being the same size after you log in. I’ll have to check what’s being stored in it and possibly reduce the size of it

You’re going to have to give a bit more detail than that. What does the error message say? It’s probably something I can fix. It shouldn’t have anything to do with you being on your phone. This site is very old and I coded it when I didn’t know what I was doing, so it has quite a lot of random bugs.