Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

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

  • 3 одговорa
  • 2 имају овај проблем
  • 34 прегледа
  • Последњи одговор послао 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?

Сви одговори (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 Власник питања
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
  • Top 25 Contributor
  • Moderator
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.