Problem: When attempting to log in to www.boiseschools.org or a specific site within it (such as adams.boiseschools.org or MyApps.BoiseSchools.org) you receive errors, or access issues to known working sites such as Google Classroom, or Google Meets and especially the following errors:
Bad Request - Request Too Long or HTTP Error 400. The size of the request headers is too long.
The solution for Boise School District accounts: Clear browser cache, cookies AND History, using the following steps.
- On your computer, open Chrome browser,
- Make certain you are syncing your @BoiseSchools account in Google Chrome NOT a @gmail.com account. (See Using Chrome with multiple accounts article)
- Ensuring that only 1 tab is open - does not matter which tab it is
- At the top right, click the Chrome Settings represented by the Ellipsis (three vertical dots),
- Near bottom, click Settings,
- On the left side of screen, Click Privacy and security
- In middle of screen click Clear browsing data
- Keyboard shortcut for the above: -While in Google Chrome with only one Chrome tab open, on the keyboard hold Ctrl+Shift and tap Delete (Chromebook press Backspace Key)
- Select Advanced on the right, (Selecting Basic will not clean up enough to fix the problem)
- Ensure the Time range selected is All time,
- Click all the check boxes, scroll down
- Click the blue CLEAR DATA,
- Close the browser - All tabs so Chrome can reset,
- Attempt to log in to the site again (do not use a saved bookmarks, instead delete the bookmark you have saved and resave).
If you still have the problem enter a help desk ticket here.
See Chrome Browser Maintenance for more information
*Students can not remove this history, only an IT staff person can delete these options, if this is needed please enter a help ticket at support.boiseschools.org.
What is it/What does it mean?
The 400 Bad Request error is an HTTP status code indicates that the request you sent to the webserver was malformed , in other words, the data stream sent by the client to the server didn't follow the rules. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed.
How do I fix a HTTP Error 400: Bad Request?
There are a number of different causes for a 400 Bad Request Error . It might be a malformed request syntax, invalid request message framing, or deceptive request routing . In some cases, the problem is on the website itself, and there's not much you can do about that. This error appear differently on different websites like the following:
|Bad Request: Error 400|
|400 Bad Request|
|HTTP Error 400 - Bad Request|
|Bad Request - Invalid URL|
|HTTP Error 400. The request hostname is invalid.|
|Bad Request. Your browser sent a request that this server could not understand.|
Fixing Bad Request: Error 400
To fix a 400 Bad Request error it is best to start diagnosing the issue from the client side itself. Complete the steps outlined in this section to help diagnose and correct the error.
- Check for errors in the URL (Is the address spelled right?)
- Clear Browser Cache and cookies.
- Clear DNS Cache.
- Check your File upload Size.
- Deactivate Browser Extensions.
- Contact the site owner to report the 404 error.
Check for errors in the URL
Check the URL and make sure it is spelled correctly or the link that was clicked on points to a URL with a specific kind of mistakes in it, like a syntax problem . It can be very easy to include unwanted characters in the URL while entering it manually in the browser. Check spelling , hyphens, page extension, etc. Also, make sure they're separated with forward slashes. Specifically, check for extra, typically non-allowed characters in the URL like a percentage character (%). Once you're sure the URL is correct, try to access it again in the browser. If you're still getting the 400 Bad Request error it's time to go for next step.
TIP: Clear Browser Cache and cookies For Android:
- Tap Chrome menu >> Settings.
- Tap (Advanced) Privacy.
- Select "All Time" from Time Range to clear your entire cache.
- Check Cookies and Site data and Cached Images and Files.
- Tap Clear data.
- Exit/quit all browser windows and re-open the browser.
Other suggestions to check:
Clear DNS Cache for Windows devices
Check your File upload Size
Deactivate Browser Extensions
If you are still encountering 400 Bad Request error , it may be caused by Browser Extensions that you have installed in your browser.
Uninstall Chrome Extensions or update them.
- Enter the following in the Chrome browsing bar:
- Chrome will display your extensions in a grid.
- To delete an extension, click the Remove button.
- Confirm by clicking Remove.
- Note District accounts are managed, some extensions can not be changed.
Lastly, Contact the site owner to report the 404 error - if it is a District site enter a help ticket listing the site you are having trouble with.
It's possible that the 400 Bad Request error actually isn't anything wrong from your end and it's something they (site owner) need to fix, in which case letting them know about it would be very helpful to solve this issue.
See also Article: Google - Chrome Browser Maintenance