Last post Jan 09, 2019 02:19 PM by mgebhard
Jan 08, 2019 01:49 PM|razzazzika|LINK
This weekend my building had a power outage. I have no idea why, but this caused our 3 web apps to stop working. I initially tried rebooting the SQL server virtual machine, and then the physical machine, but that didn't do anything.
The web apps are able to read data from the database no problem, but when they try to save, it produces an error 400. -
If the problem continues, contact the site owner.
I was at a loss yesterday and could not figure out why this was not working. I always use chrome for general day to day use, and have never had a problem with it before. I dusted off firefox this morning just because I was curious and lo and behold the
web app worked perfectly. Edge produced the same results. This error 400 is only happening on Chrome and no other browsers.
Did Chrome release an update that broke something over the weekend? Is it something with my infrastructure that somehow is not allowing requests from chrome through?
I'm at a complete loss here because as of Saturday, this was working, as I was doing development on one of the apps when the power outage occurred on Sunday I was not able to use the apps. I still want to believe it has something to do with that, but I have
no idea. Is there something I need to add to the code to all of these programs to get them to work again?
Thanks for your time
Jan 08, 2019 02:46 PM|mgebhard|LINK
A 400 error means there is an issue with the request sent from the client.
First, try deleting cookies. Try a different machine If that does not help and you feel this is an issue with your installation of chrome than uninstall and reinstall Chrome.
Jan 09, 2019 06:03 AM|Sherry Chen|LINK
Hi razzazzika ,
a 400 Bad Request Error indicates that the request sent by the client was invalid for one reason or another, it’s entirely possible the issue steps from the client. Your client may be trying to send a file that’s too big,
the request could be malformed in some way, the request HTTP headers could be invalid, and so forth. We’ll explore some of these scenarios (and potential solutions) down below, but be aware that, even though the 400 Bad Request Error is
considered a client error response, it doesn’t inherently mean we can rule out either the client nor the server as the root of the problem. In these scenarios, the server is still the network object that
is producing the 400 Bad Request Error, and returning it as the HTTP response code to the client, but it could be that the client is causing the issue in some way.
400 Bad Request Error
client error response
You could refer to
the docs about Troubleshooting on the Client-Side/Server-Side to fix 400 Bad Request Error
Best Regards ,
Jan 09, 2019 11:04 AM|yogyogi|LINK
This error 400 is only happening on Chrome and no other browsers.
Try running the website in Chrome's incognito window and check if your problem solves or not.
Jan 09, 2019 01:14 PM|razzazzika|LINK
Ok so this worked.
I had originally thought this problem was system-wide, because it started when the plant lost power.
We have two programmers here only, and the other programmer was experiencing the same problem. I had someone else who never used the system before try to go in and it worked fine for them.
My co-worker was able to get his to work by deleting his cookies and cache, but the same is not happening for mine. I was thinking of uninstalling and reinstalling Chrome.
Apologies, i thought this was an ASP question but it was not at all.
Jan 09, 2019 02:19 PM|mgebhard|LINK
It's still an application issue related to cookie most likely. That's why incognito works.