14,953
edits
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
HTTP status code | HTTP status code | ||
{{LanguageSwitcher | content = [[Troubleshooting of HTTP errors | EN]], [[Troubleshooting of HTTP errors in Mandarin | 漢字]] }} | |||
__TOC__ | __TOC__ | ||
| Line 8: | Line 10: | ||
Root cause of 400 Bad Request. HTTP Error 400. The request is badly formed. | Root cause of 400 Bad Request. HTTP Error 400. The request is badly formed. | ||
* "the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing)" | * "the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing)" | ||
Possible solution: | |||
* Modify the request headers | * Modify the request headers | ||
== 403 Forbidden Error == | == 403 Forbidden Error == | ||
[[How to fix the 403 forbidden error]] | See: [[How to fix the 403 forbidden error]] | ||
== 404 File Not Found == | == 404 File Not Found == | ||
Solution: Check if the accessed link is correct, see "404 Not Found | Possible solutions for pages not found" | |||
== 405 Method Not Allowed Error == | == 405 Method Not Allowed Error == | ||
Solution: Check if the accessed file or resource supports the HTTP protocol being used. For example, if the resource is restricted to POST requests but you're using GET. | |||
== 414 Request-URI Too Large == | == 414 Request-URI Too Large == | ||
Solution: Change the request protocol to POST instead of GET | |||
== 415 Unsupported Media Type == | == 415 Unsupported Media Type == | ||
Solution: "Set the Content-Type or Content-Encoding in the request or direct access to the data." For example: When encountering this error with RESTful API, a possible solution is to add to the HTTP Headers: | |||
<pre> | <pre> | ||
Content-Type: application/json | Content-Type: application/json | ||
| Line 36: | Line 36: | ||
== 429 Too Many Requests == | == 429 Too Many Requests == | ||
Cause: | |||
* | * Accessing website resources too frequently | ||
Solutions: | |||
* | * Adjust access frequency | ||
* If accessing a web service API, read the documentation to understand the API's rate limits | |||
== 502 Bad Gateway == | == 502 Bad Gateway == | ||
Cause: | |||
* Error occurs between network devices, users cannot directly handle it. | |||
* | |||
Solutions: | |||
* | * Bypass browser cache, refresh the page | ||
* Try reconnecting after a while | |||
== Error 1020: Access Denied == | == Error 1020: Access Denied == | ||
* | * See link for understanding how to resolve Error 1020 Access Denied to get your website back online | ||
<pre> | <pre> | ||
| Line 64: | Line 58: | ||
</pre> | </pre> | ||
https://http.cat/200.jpg | |||
From HTTP Cats | |||
Related websites | Related websites: | ||
* [https://httpstatusdogs.com/ HTTP Status Dogs] | * [https://httpstatusdogs.com/ HTTP Status Dogs] | ||
== Other | == Other possible root causes == | ||
* CDN ( | * CDN (Content delivery network) | ||
== Related pages == | == Related pages == | ||