Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Error message: 400 Bad Request Request Header Or Cookie Too Large nginx/1.18.0 (Ubuntu)

  • 3 respostas
  • 2 have this problem
  • 11 views
  • Last reply by cor-el

shaw.deborah
shaw.deborah
more options

When I click a link on a website, a new Firefox tab opens with this message: 400 Bad Request Request Header Or Cookie Too Large nginx/1.18.0 (Ubuntu). This is new behavior; it was working fine until yesterday. Can you tell me how to fix it?

When I click a link on a website, a new Firefox tab opens with this message: 400 Bad Request Request Header Or Cookie Too Large nginx/1.18.0 (Ubuntu). This is new behavior; it was working fine until yesterday. Can you tell me how to fix it?

All Replies (3)

jonzn4SUSE
jonzn4SUSE
  • Top 10 Contributor
more options

Steps to replicate the issue and screenshots please. Try downloading Firefox from Mozilla, run it from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

shaw.deborah
shaw.deborah Question owner
more options

@jonzn4SUSE,

Thanks for your reply.

I cleared the cache. Doing this logged me out of other websites I was using, but it also cleared up the issue.

Thanks again.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Note that this is usually a problem with the cookies and clearing the cookies for this website via the padlock should fix this.