Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

I keep getting: Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit(print page)

  • 5 svar
  • 10 har dette problem
  • 1 visning
  • Seneste svar af robinf24300

more options

This has just started happening: every time I try to print from a remote website (thetimes.co.uk) I get this message:

Bad Request

Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit.

It is not the website, as the request works from Microsoft Edge.

I can't see any changes to the parameters which might have affected this.

Any ideas please?

This has just started happening: every time I try to print from a remote website (thetimes.co.uk) I get this message: Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. It is not the website, as the request works from Microsoft Edge. I can't see any changes to the parameters which might have affected this. Any ideas please?

Valgt løsning

This issue can be caused by corrupted cookies.

  • check the permissions for the domain in the currently selected tab in "Tools -> Page Info -> Permissions"

Clear the cache and remove the cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).

"Clear the cache:

  • Options/Preferences -> Privacy & Security -> Cached Web Content: "Clear Now"

"Remove the cookies" from websites that cause problems.

  • Options/Preferences -> Privacy & Security -> "Use custom settings for history" -> Cookies: "Show Cookies"

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 if 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.

Læs dette svar i sammenhæng 👍 2

Alle svar (5)

more options

Did you check with the remote website about the print issue? If it is going through them maybe they are blocking something.

more options

The problem is that it works fine with Edge, which I don't normally use. I've never come across `Bad Request' before, and the fact that I can print from the website using Edge suggests it's a Waterfox bug.

more options

Hi All, Evidently the remote website has put in a fix overnight -- it works fine this morning. Thanks FYI.

more options

Valgt løsning

This issue can be caused by corrupted cookies.

  • check the permissions for the domain in the currently selected tab in "Tools -> Page Info -> Permissions"

Clear the cache and remove the cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).

"Clear the cache:

  • Options/Preferences -> Privacy & Security -> Cached Web Content: "Clear Now"

"Remove the cookies" from websites that cause problems.

  • Options/Preferences -> Privacy & Security -> "Use custom settings for history" -> Cookies: "Show Cookies"

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 if 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.

more options

Many thanks Corel. I will check cached web content and make sure the problem has gone away. Tks.