Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók
A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.
Archivált

Unable to Login to SSA.Gov Site

Firefox Lassú kapcsolat
jscher2000 -... megválaszolva
Nikon1
Nikon1

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.

Összes válasz (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer

> 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?