Bad Request - server could not understand.
- Thread starter w3services_net
- Start date
Just try to access below URLs you will observe the issue. Refresh the same URL 2-3 times.. it will start working the same URL again. But why 400 Error coming not able to find it.
https://webrunnr.com/contact-us
Click on random pages. I am sure you get the error as I am getting. Even monitoring tools like uptime also reporting the same but again within minutes they also report URL working.
No error in logs.
https://webrunnr.com/contact-us
Click on random pages. I am sure you get the error as I am getting. Even monitoring tools like uptime also reporting the same but again within minutes they also report URL working.
No error in logs.
400 Bad Request Error: What It Is and How to Fix It https://airbrake.io/blog/http-errors/400-bad-request
Since the 400 Bad Request Error is a client error response code, it’s best to start by troubleshooting any potential client-side issues that could be causing this error.
400 should show up in error log similar to:
2018-04-16 14:27:24.707114 NOTICE [162.*.*.*:20689] Status 400: Http request header is too big, abandon!
2018-04-16 14:27:30.324454 NOTICE [108.*.*.*:25277] Status 400: Http request header is too big, abandon!
2018-04-16 14:27:30.753616 NOTICE [108.*.*.*:11391] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:04.983279 NOTICE [172.*.*.*:27043] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:09.189628 NOTICE [172.*.*.*:36797] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:14.921465 NOTICE [162.*.*.*:9799] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:16.782820 NOTICE [162.*.*.*:15187] Status 400: Http request header is too big, abandon!
Since the 400 Bad Request Error is a client error response code, it’s best to start by troubleshooting any potential client-side issues that could be causing this error.
400 should show up in error log similar to:
2018-04-16 14:27:24.707114 NOTICE [162.*.*.*:20689] Status 400: Http request header is too big, abandon!
2018-04-16 14:27:30.324454 NOTICE [108.*.*.*:25277] Status 400: Http request header is too big, abandon!
2018-04-16 14:27:30.753616 NOTICE [108.*.*.*:11391] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:04.983279 NOTICE [172.*.*.*:27043] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:09.189628 NOTICE [172.*.*.*:36797] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:14.921465 NOTICE [162.*.*.*:9799] Status 400: Http request header is too big, abandon!
2018-04-16 14:31:16.782820 NOTICE [162.*.*.*:15187] Status 400: Http request header is too big, abandon!
The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. 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. The main thing to understand is that the 400 Bad Request error is a client-side error.
The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.
The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.