NetID Login - How to Fix a "Stale Request" Error

This document describes what to do if you receive a 400 Bad Request error message upon loading the UW-Madison NetID Login page.

Problem

When you are attempting to log in to a UW Madison service or a link that requires NetID authentication, you may see the following error:

Stale Request Error

Solutions

  • Make sure you are attempting to use a valid link. If you are using a bookmark, try getting to the site another way as bookmarks can cause this error.
  • If you are using Safari on a Mac, follow the instructions in NetID Login - "Stale Request" Error in Safari first to make sure your browser is not blocking all cookies, which can prevent NetID login from functioning properly.
  • If neither of these solutions work, completely restart the browser so that all previous windows and tabs have been closed. In some cases, this alone can fix the issue. If this does not work, then the issue can usually be resolved by clearing your browser's cache and cookies. Click the browser you are using below to find instructions for clearing your browser's cache and cookies.

If it does not appear to be an issue with the browser, it could be a network issue. Please try using a a different network or cellular data. If none of these work, consider downloading WiscVPN: WiscVPN GlobalProtect (Windows) - Installing/Updating, WiscVPN GlobalProtect (macOS) - Installing

Currently, certain versions of Firefox will give this error even after completing possible troubleshooting. Try using a different browser, such as Google Chrome.

Desktop Web Browsers

Clearing the browser cache prevents you from using old/out-of-date versions of websites and protects your personal information. It also helps running some applications better on your computer by freeing up space.

Note: Make sure you set the Time Range to the "All Time" or "Everything" options when available to clear all data. Please save any unpublished work before proceeding; you will be logged out of all sites and applications and will need to re-authenticate.

Table with browser name and links to Windows documents and macOS documents.
Browser Windows Document Link macOS Document Link

Google Chrome		 Chrome (Windows) - Clearing Cache and Cookies Chrome (Mac) - Clearing Cache and Cookies

Firefox		 Firefox 57+ (Windows) - Clearing Cache and Cookies Firefox 21+ (Mac) - Clearing Cache and Cookies

Safari		 Safari (Windows) - Clearing Cache and Cookies Safari 10.0.1+ (Mac) - Clearing Cache and Cookies

Opera		 Opera (Windows) - Clearing Cache and Cookies Opera 28.0 (Mac) - Clearing Cache and Cookies

Microsoft Edge		 New Edge (Win 10, 8, 7, MacOS) - Clearing Cache and Cookies New Edge (Win 10, 8, 7, MacOS) - Clearing Cache and Cookies

Mobile Web Browsers

Table with mobile Operating System and corresponding documents on clearing cache and cookies.
Operating System Document Link
Android Icon
Android		 Android 15 (Vanilla Ice Cream) - Clearing Cache and Cookies on Google Chrome
iOS Icon
iOS		 Safari (iOS) - Clearing Cache and Cookies

Legacy Versions

Website DNS (Domain Name System) Changes

DNS changes for websites can be cached separately for users on browser and machine. If the website you are trying to access has been moved to a new destination, you may need to flush your local DNS cache in addition to clearing browser cache and cookies before you can receive the updated website destination.

External instructions on how to flush your local DNS cache for Windows, Mac, and Linux can be found here. If you do not have administrative privileges on your machine, restarting the device can also effectively flush your local DNS cache.

If you are still experiencing issues after completing those steps, contact the DoIT Help Desk. See: Get Help from DoIT

See Also


Keywords:
problem login log in error account browser stale request 
Doc ID:
79133
Owned by:
Help Desk KB Team in DoIT Help Desk
Created:
2018-01-10
Updated:
2026-06-02
Sites:
DoIT Help Desk