Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Unable to Login to SSA.Gov Site

Nikon1
Nikon1
dalše nastajenja

Whenever I login to the web site "SSA.GOV" and click the login button, the next screen presented in Firefox is: "Bad Request

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

If I go to a Private Window, type in the SSA.Gov and then select the Login page, I am presented with the correct page and can then supply my information and login.

Whenever I login to the web site "SSA.GOV" and click the login button, the next screen presented in Firefox is: "Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit.'' If I go to a Private Window, type in the SSA.Gov and then select the Login page, I am presented with the correct page and can then supply my information and login.

Wšě wotmołwy (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
dalše nastajenja

> Size of a request header field exceeds server limit.

The header field most notorious for growing and growing is the cookies field. Since private windows do not re-use the cookies from regular windows, your private window test supports this theory.

I suggest trying to clear your cookies for that site. Here's how:

  • While viewing a page on the site, click the lock icon at the left end of the address bar.
  • After a moment, a "Clear Cookies and Site Data" button should appear at the bottom.
  • Go ahead and click that. Firefox will ask you to confirm; go ahead and confirm.

Then try reloading the page and logging in again. Does that help?