We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

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

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

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

  • 3 svar
  • 2 har dette problem
  • 21 visninger
  • Seneste svar af 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?

Alle svar (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 Spørgsmålsstiller
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.