Request failed with status code 400

03.09.202203.09.2022 admin 0 Comments

Request failed with status code 400

request failed with status code 400

I am running server in nodejs, while executing the code of server i am getting an error as «(node:7692) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Request failed with status code 400 (node:7692) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code».

this is my serverrender.js code

this is my srver.js code

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You should add a catch to the get call:

You need to enclose the opening parentheses of the config variable.

Error: Request failed with status code 400. Differences between sending in POSTMAN and in the application

In POSTMAN it works:

In the function submit method POST, when the form is submit, it does not work. I have error:

Error: Request failed with status code 400 at createError (createError.js?2d83) at settle (settle.js?467f) at XMLHttpRequest.handleLoad (xhr.js?b50d)

In tab Network in response I have:

Login

What are the differences between sending in POSTMAN and in the application? Contents of the body convert to a string?

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Axios handles error differently.

To find out what really is the issue.

You should use error.request to check if the request you made has error

and use error.response to get the error feedback from the server

The code is stating in the Content-Type that the body will be URL string encoded, but in the body it is given a JavaScript object. It doesn’t seem like the Axios client turns that body object into a url-encoded value (ie from to «a=5&b=2» ). The code needs a function convert that. A popular one is qs.

Localhost:3000/api/products 404 Error You did not create res.get(«/api/products») on server.js or you did not set the proxy. check below for proxy setting.

Proxy error: could not proxy request /api/products Check this:

AxiosError : Request failed with status code 400 (in React JS)

I am trying to post comments using axios. When I submit my datas entered in the form, I see this error in the console :

Here is my code :

Have a look on my server :

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You’re not sending anything to your API. CommentsAPI.create(YOUR COMMENT HERE)

Also, in your server you will need to return helpful error message. Like ‘Hey, there is no message, please send a message in the payload’. That will help you understand better what’s going on.

For anyone else, who is facing the same issue, try changing your get http request to post, if you are sending data from body that has a list. Hope this helps.

If you receive a 400 (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_client_errors), it means that the sever received your request but the content was not valid. Read the documentation of the API to be sure you send the correct payload.

By default, if Axios receives something other than a 2xx, it will throw an exception

Request failed with status code 400 with axios

I am trying to use the login API I made using node, however, whenever I call the API using Axios, it gives me a request failed in the console.

This is how I use axios to call my method:

And this is my login page and console :

This is my backend configuration:

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

please try this

well, I do not know how is the backend configured, but you could start by stringyfing yow body

If that does not do any change, then change the header instead

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

400 Bad Request: The request cannot be fulfilled due to bad syntax.

In this case, your client sent you an XML payload that had an invalid zip code, which is a form of invalid syntax; therefore, sending a 400 Bad Request is an appropriate error code to return in this situation.

In addition, Wikipedia cites RFC-4918 as a resource on this topic. From this document, you’ll find the following information:

Servers MAY reject questionable requests (even though they consist of well-formed XML), for instance, with a 400 (Bad Request) status code and an optional response body explaining the problem.

Since your request is well-formed (the XML isn’t bad, it just contains semantically incorrect information) you may reject the content with status code 400. The word *may* suggests that there are other options.

While you might be tempted to use status code 422, this would not be correct in this situation, since the invalid zip code does not meet the criteria to be a semantic error. Read below.

422 Unprocessable Entity (WebDAV; RFC 4918): The request was well-formed but was unable to be followed due to semantic errors.

Syntax errors occur during the parsing of input code, and are caused by grammatically incorrect statements. Typical errors might be an illegal character in the input, a missing operator, two operators in a row, two statements on the same line with no intervening semicolon, unbalanced parentheses, a misplaced reserved word, etc.

Semantic errors occur during the execution of the code, after it has been parsed as grammatically correct. These have to do not with how statements are constructed, but with what they mean. Such things as incorrect variable types or sizes, nonexistent variables, subscripts out of range, and the like, are semantic errors.

Your invalid zip code is neither a syntax error nor a semantic error; thus, it’s reasonable to rule out status code 422 as an option.

To answer your question, status code 400 is appropriate; however, you may have other options as well.

HTTP 400 Bad Request (Request Header too long) responses to HTTP requests

When an HTTP request that needs Kerberos authentication is sent to a website that’s hosted on Internet Information Services (IIS) and is configured to use Kerberos authentication, the HTTP request header would be very long. This article helps you work around the HTTP 400 error that occurs when the HTTP request header is too long.

Original product version: В Windows Server 2016
Original KB number: В 2020943

Symptoms

An HTTP request that needs Kerberos authentication is sent from a browser to a website that’s hosted on IIS. The website is configured to use Kerberos authentication. However, instead of receiving the expected webpage, you receive an error message that resembles the following one:

This response could be generated by any HTTP request that includes Windows Remote Management (WinRM).

Cause

This issue may occur if the user is a member of many Active Directory user groups.

The HTTP request to the server contains the Kerberos token in the WWW-Authenticate header. The header size increases together with the number of user groups. If the HTTP header or packet size increases past the limits that are configured on the server, the server may reject the request and send an error message as the response.

Workaround 1: Decrease the number of Active Directory groups

Decrease the number of Active Directory groups that the user is a member of.

Workaround 2: Set MaxFieldLength and MaxRequestBytes registry entries

Increase the settings for the MaxFieldLength and the MaxRequestBytes registry entries on the server so that the user’s request headers don’t exceed these values. To determine the appropriate settings, use the following calculations:

Calculate the size of the user’s Kerberos token by using the formula described in the following article:
Problems with Kerberos authentication when a user belongs to many groups.

Set the value of MaxFieldLength and MaxRequestBytes on the server to 4/3 * T bytes, where T is the user’s token size in bytes. HTTP encodes the Kerberos token by using base64 encoding.

This replaces every three bytes in the token with four base64-encoded bytes. Changes that are made to the registry do not take effect until you restart the HTTP service. Additionally, you may have to restart any related services, such as IIS services.

Depending on your application environment, you might also work around this problem by configuring the website to use Windows NT LAN Manager (NTLM) instead of Kerberos. Some application environments require Kerberos authentication to be used for delegation. We consider Kerberos authentication to be more secure than NTLM. And we recommend that you don’t disable Kerberos authentication before you consider the security and delegation ramifications.

More information

By default, there is no MaxFieldLength registry entry. This entry specifies the maximum size limit of each HTTP request header. The MaxRequestBytes registry entry specifies the upper limit for the total size of the Request line and the headers. Typically, this registry entry is configured together with the MaxRequestBytes registry entry. If the MaxRequestBytes value is lower than the MaxFieldLength value, the MaxFieldLength value is adjusted. In large Active Directory environments, users may experience logon failures if the values for both these entries aren’t set to a sufficiently high value.

For IIS 6.0 and later, the MaxFieldLength and MaxRequestBytes registry keys are located at the following sub key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

Set the key values as shown in the following table:

Name	Value Type	Value Data
MaxFieldLength	DWORD	(4/3 * T bytes) + 200
MaxRequestBytes	DWORD	(4/3 * T bytes) + 200

You can also set the registry keys to their maximum values, as shown in the next table. Consider all potential security ramifications before you make any changes to the registry settings.

Name	Value Type	Value Data
MaxFieldLength	DWORD	65536 (Dec) or 10000 (Hex)
MaxRequestBytes	DWORD	16777216 (Dec) or 1000000 (Hex)

Changing these registry keys should be considered to be extremely dangerous. These keys allow larger HTTP packets to be sent to IIS. This, in turn, may cause Http.sys to use more memory. Therefore, such changes can increase the computer’s vulnerability to malicious attacks.

If MaxFieldLength is set to its maximum value of 64 KB, the MaxTokenSize registry value should be set to 3/4 * 64 = 48 KB. For more information about the MaxTokenSize setting, see Problems with Kerberos authentication when a user belongs to many groups.

Getting 400 error Bad request using axios

I am using axios and getting a 400 bad request error. I am using react-redux and trying to send a post request to localhost:3000/posts. Here is the code that I am using.

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

i was also getting this error, the issue was not with server or with axios or proxy url. The issue was i wasn’t sending the correct data from my react application. For Example i supposed to send:

what i was sending is:

this caused api don’t understand name field, as i provided email as the key in api.

so if you are still facing the issue try to check if you are sending the correct data.

For every post request, the client first sends an OPTIONS request to check whether the server is ready to accept the connection. You should also allow the server to accept options request. If you have not allowed use the below lines in case of node server

Linked

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

request failed with status code 400

this is my serverrender.js code

this is my srver.js code

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You should add a catch to the get call:

You need to enclose the opening parentheses of the config variable.

400 vs 422 for Client Error Request

I’ve read a lot of posts and articles regarding proper http status code to return for client request error. Others suggest to use 400 as it has been redefined in RFC 7231 though I’m not sure if the example given covers all the client error in my mind because the examples are syntactic.

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request
message framing, or deceptive request routing).

I did find this statement in the Appendix B of the rfc 7231:

The 400 (Bad Request) status code has been relaxed so that it isn’t
limited to syntax errors. (Section 6.5.1)

Does this mean that I can consider any type of client error a bad request? Would it be better to use 400 for client requests and just specify a more specific error in the message?

On the other hand, others say that it’s better to use 422 (Unprocessable Entity). While this is more focused on semantics, it’s only listed in [RFC 4918][2] which is a webDAV extension for http/1.1

The 422 (Unprocessable Entity) status code means the server
understands the content type of the request entity (hence a
415(Unsupported Media Type) status code is inappropriate), and the
syntax of the request entity is correct (thus a 400 (Bad Request)
status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML
request body contains well-formed (i.e., syntactically correct), but
semantically erroneous, XML instructions.

Can I use this webDAV extension codes to handle my http requests? In the case of 422, can I use it even though it’s not in the core http codes.

Should I use 400 or 422 for my client error?

Here are the possible client error I have in mind:

Any informative response will be highly appreciated. Thanks a lot, guys!

Update: I checked google api errors and they are not using 422. On the other hand, Twitter uses 422. I’m more confused than ever >. Follow

400 BAD request HTTP error code meaning?

I have a JSON request which I’m posting to a HTTP URL.

Should this be treated as 400 where requestedResource field exists but «Roman» is an invalid value for this field?

Should this be treated as 400 where «blah» field doesn’t exist at all?

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn’t follow the rules.

In the case of a REST API with a JSON payload, 400’s are typically, and correctly I would say, used to indicate that the JSON is invalid in some way according to the API specification for the service.

By that logic, both the scenarios you provided should be 400s.

Imagine instead this were XML rather than JSON. In both cases, the XML would never pass schema validation—either because of an undefined element or an improper element value. That would be a bad request. Same deal here.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

Selecting a HTTP response code is quite an easy task and can be described by simple rules. The only tricky part which is often forgotten is paragraph 6.5 from RFC 7231:

Except when responding to a HEAD request, the server SHOULD send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.

Rules are as following:

So in your case I’d returned 400 error and something like this if «Roman» is obtained from user input and client must have specific reaction:

or a more generic error, if such situation is a bad logic error in a client and is not expected, unless developer made something wrong:

400 BAD request HTTP error code meaning?

I have a JSON request which I’m posting to a HTTP URL.

Should this be treated as 400 where requestedResource field exists but «Roman» is an invalid value for this field?

Should this be treated as 400 where «blah» field doesn’t exist at all?

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn’t follow the rules.

By that logic, both the scenarios you provided should be 400s.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

Selecting a HTTP response code is quite an easy task and can be described by simple rules. The only tricky part which is often forgotten is paragraph 6.5 from RFC 7231:

Except when responding to a HEAD request, the server SHOULD send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.

Rules are as following:

So in your case I’d returned 400 error and something like this if «Roman» is obtained from user input and client must have specific reaction:

or a more generic error, if such situation is a bad logic error in a client and is not expected, unless developer made something wrong:

request failed with status code 400

this is my serverrender.js code

this is my srver.js code

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You should add a catch to the get call:

You need to enclose the opening parentheses of the config variable.

400 BAD request HTTP error code meaning?

I have a JSON request which I’m posting to a HTTP URL.

Should this be treated as 400 where requestedResource field exists but «Roman» is an invalid value for this field?

Should this be treated as 400 where «blah» field doesn’t exist at all?

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn’t follow the rules.

By that logic, both the scenarios you provided should be 400s.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

Selecting a HTTP response code is quite an easy task and can be described by simple rules. The only tricky part which is often forgotten is paragraph 6.5 from RFC 7231:

Except when responding to a HEAD request, the server SHOULD send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.

Rules are as following:

So in your case I’d returned 400 error and something like this if «Roman» is obtained from user input and client must have specific reaction:

or a more generic error, if such situation is a bad logic error in a client and is not expected, unless developer made something wrong:

Which status code is correct 404 or 400 and when to use either of these?

What is the status code should return when an object inside my resource is not available?

What should be the response code if the scheme with id 15 does not exist?400 or 404?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I don’t think 404 is suitable for this situation if the request has been performed to a URL that points to a resource that does exist. The problem is in the payload, so 404 has nothing to do with it.

The syntax of the JSON document is valid, so 400 is not suitable either.

What you have is an unprocessable entity due to invalid data, so 422 would be the best alternative here. Keep reading for a more detailed explanation.

Not found and Bad request

Assuming that the request has been performed to a URL that locates a valid resource (that is, a resource that exists), returning 404 is not suitable for this situation and it may yield misunderstanding:

The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists. A 404 status code does not indicate whether this lack of representation is temporary or permanent; the 410 (Gone) status code is preferred over 404 if the origin server knows, presumably through some configurable means, that the condition is likely to be permanent.

Returning 400 with a descriptive message in the payload would be suitable for this situation if the JSON was malformed, but that’s not the case:

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Unprocessable entity

As a matter of fact, what you have is an entity that cannot be processed by the server due to invalid data. So returning 422 and details about the error in the response payload would be the most suitable approach for this situation:

The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.

Just read JSON when it says XML.

You also may find this answer helpful.

Problem details for HTTP APIs

HTTP status codes are sometimes not sufficient to convey enough information about an error to be helpful. The RFC 7807 defines simple JSON and XML document formats to inform the client about a problem in a HTTP API.

It also defines the application/problem+json and application/problem+xml media types.

Picking the right 4xx status code

The following diagram (extracted from this page) is pretty insightful when it comes to picking the most suitable 4xx status code. Hopefully it will help you:

What is the status code should return when an object inside my resource is not available?

Michael Kropat put together a pretty good flowchart for choosing an HTTP status code.

The first step is to determine whether or not you have an error at all. It’s perfectly reasonable for resource schema to include optional elements. If that’s appropriate for your circumstances, then just use a 200 and call it a day.

On the other hand, if it is an error, you now need to evaluate the cause of the fault.

If the problem stems from the request, then you should be looking at entries in the 4xx class of status code.

The 4xx (Client Error) class of status code indicates that the client seems to have erred.

These are all variations of a problem with the HTTP Request itself; the client shouldn’t have requested that resource, or the client needed to include different information in the request, or. lots of different variations spelled out by RFC 7231.

The heuristic here is that the client can fix things by sending a different request.

On the other hand, if the request was fine, but the server can’t respond correctly right now, then you should be looking at the 5xx class

The 5xx (Server Error) class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method.

The 5xx class is much smaller; 500 is almost always the correct choice, the protocol doesn’t care very much about communicating the details to the client because there’s nothing the client can to address a server issue.

My best guess, from your example, is that you should either be sending a 500 response with a payload that contains «an explanation of the error situation», or you should be sending a 200 response with a payload that includes the representation of the resource, even if that representation doesn’t include all of the optional elements.

Исправление ошибки 400 Bad request

400 bad request error – одна из самых популярных проблем, с которой может столкнуться абсолютно любой пользователь, проводящий много времени на просторах интернета. В отличии от ошибки 500, которую мы недавно описывали, данная неприятность, характеризуется следующими особенностями:

Естественно, что мы постараемся помочь нашим читателям и с решением этой проблемы.

Что такое 400 bad request?

Попробуем узнать на официальном сайте операционной системы Windows, что именно обозначает данная неприятность, и как ее исправлять. В перечне возможных проблем находим перевод «routebuildservice 400 bad request – ошибочный запрос. И все. То есть, ребята из Microsoft не хотят помогать в данной ситуации. Ну и ладно – зато мы знаем, как исправить 400 bad request.

400 bad request error – методика исправления

Одной из особенностей данной неприятности является возможность возникновения какой-либо ошибки со стороны владельца сайта или интернет-провайдера. К сожалению, но при таком варианте от пользователя совершенно ничего не зависит. Конечно, компания с хорошей репутацией всегда старается предупреждать своих клиентов о возникновении подобных неприятностей. Но, как показывает практика, в нашей стране делается это очень редко. Поэтому рекомендации для пользователя будут такие – постараться самостоятельно получить требуемую информацию:

Если проблема возникает не по вине удаленного сервера, то следует внимательно еще раз перечитать сообщение, возникающее на экране. Ели оно выглядит так — 400 bad request request header or cookie too large, то решению очень простое:

Заключительный этап, если предыдущие шаги не помогли решить поставленную задачу, касается изменения настроек используемого антивирусного ПО и брандмауэра Windows. Что требуется сделать, чтобы окончательно решить ситуацию с 400 bad request error:

Проблема решена. Данная неприятность, действительно, очень особенная. Поэтому не стоит долго искать ответа на вопрос — 400 bad request: что это означает, — а сразу приступать к лечению.

Один из эффективных способов борьбы с ошибкой 400 можно увидеть на тематическом видео — обязательно посмотрите:

SSRS error message: The request failed with HTTP status 400: Bad Request

An admin updated the dev and test servers by adding Report Viewer 2012 for me.

I have no access to the test server, but am admin on the dev server. I can work with someone who has admin access to the test server, but I will need to know what to look for.

My SSRS reports deployed from Visual Studio 2012 were converted to Microsoft.ReportViewer.WebForms 11.0 from version 10.0.

These reports work just find on my dev server, but when my QA tester uses the report, the first time the page shows the error «The request failed with HTTP status 400: Bad Request.»

Note that no report is loaded by default.

Once we request a report, this report shows up properly and the error message disappears.

I am trying to remove this initial error message, as it is confusing for the end user.

Does anybody have any idea?

Thanks in advance!

Below is the code as shown by developer tools.

CORS Errors only with 400 bad request react fetch request

I’m trying to make ‘POST’ request in react but i’m getting a few problems regarding CORS. I was just following what console says and fix them in server side [which is PHP ] and client side everything works fine when the status is 200 but when status 400 it shows

login:1 Failed to load http://192.168.0.102/API/: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://localhost:3000’ is therefore not allowed access. The response had HTTP status code 400. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.

I’ve tried to add mode: ‘no-cors’ but that’s doesn’t work it shows

Uncaught (in promise) SyntaxError: Unexpected end of input

Server Side ‘PHP Slimframework’ headers:

Client Side

src/actions/userActions.js

src/components/layout.js

here screenshot getting this error only with bad request like 400

Please let me know if I miss out any information.

If this has already been asked, I would greatly appreciate if you are able to point me in the right direction.

Error: Request failed with status code 400 in react-native with axios

I’m getting err: request failed with status code 400. What am I doing wrong here?

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

using qs and changing the headers solved my problem.

Good that you managed to solve, for future reference, if you have a 400 Bad Request error, i found really useful to print the error.response.data for more meaningful error messages.

Not the answer you’re looking for? Browse other questions tagged react-native or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

HTTP response status codes

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:

The below status codes are defined by section 10 of RFC 2616. You can find an updated specification in RFC 7231.

Note: If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server’s software.

Information responses

This interim response indicates that the client should continue the request or ignore the response if the request is already finished.

This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.

This code indicates that the server has received and is processing the request, but no response is available yet.

This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.

Successful responses

The request succeeded. The result meaning of «success» depends on the HTTP method:

The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.

The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the 200 OK response is preferred to this status.

There is no content to send for this request, but the headers may be useful. The user agent may update its cached headers for this resource with the new ones.

Tells the user agent to reset the document which sent this request.

This response code is used when the Range header is sent from the client to request only part of a resource.

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

Used inside a response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Redirection messages

The request has more than one possible response. The user agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)

The URL of the requested resource has been changed permanently. The new URL is given in the response.

This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.

Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.

This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.

The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

Client error responses

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Although the HTTP standard specifies «unauthorized», semantically this response means «unauthenticated». That is, the client must authenticate itself to get the requested response.

This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.

The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.

The request method is known by the server but is not supported by the target resource. For example, an API may not allow calling DELETE to remove a resource.

This response is sent when the web server, after performing server-driven content negotiation, doesn’t find any content that conforms to the criteria given by the user agent.

This is similar to 401 Unauthorized but authentication is needed to be done by a proxy.

This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.

This response is sent when a request conflicts with the current state of the server.

This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for «limited-time, promotional services». APIs should not feel compelled to indicate resources that have been deleted with this status code.

Server rejected the request because the Content-Length header field is not defined and the server requires it.

The client has indicated preconditions in its headers which the server does not meet.

Request entity is larger than limits defined by server. The server might close the connection or return an Retry-After header field.

The URI requested by the client is longer than the server is willing to interpret.

The media format of the requested data is not supported by the server, so the server is rejecting the request.

The range specified by the Range header field in the request cannot be fulfilled. It’s possible that the range is outside the size of the target URI’s data.

This response code means the expectation indicated by the Expect request header field cannot be met by the server.

The server refuses the attempt to brew coffee with a teapot.

The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.

The request was well-formed but was unable to be followed due to semantic errors.

The resource that is being accessed is locked.

The request failed due to failure of a previous request.

Indicates that the server is unwilling to risk processing a request that might be replayed.

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).

The origin server requires the request to be conditional. This response is intended to prevent the ‘lost update’ problem, where a client GET s a resource’s state, modifies it and PUT s it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.

The user has sent too many requests in a given amount of time («rate limiting»).

The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.

The user agent requested a resource that cannot legally be provided, such as a web page censored by a government.

Server error responses

The server has encountered a situation it does not know how to handle.

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.

This error response is given when the server is acting as a gateway and cannot get a response in time.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.

The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.

The server detected an infinite loop while processing the request.

Further extensions to the request are required for the server to fulfill it.

Indicates that the client needs to authenticate to gain network access.

400 BAD request HTTP error code meaning?

I have a JSON request which I’m posting to a HTTP URL.

Should this be treated as 400 where requestedResource field exists but «Roman» is an invalid value for this field?

Should this be treated as 400 where «blah» field doesn’t exist at all?

10 Answers 10

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn’t follow the rules.

By that logic, both the scenarios you provided should be 400s.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

Selecting a HTTP response code is quite an easy task and can be described by simple rules. The only tricky part which is often forgotten is paragraph 6.5 from RFC 7231:

Except when responding to a HEAD request, the server SHOULD send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.

Rules are as following:

So in your case I’d returned 400 error and something like this if «Roman» is obtained from user input and client must have specific reaction:

or a more generic error, if such situation is a bad logic error in a client and is not expected, unless developer made something wrong:

Как исправить ошибку 400 Bad или Invalid Request HTTP?

Связь между клиентским браузером и веб-сервером может иметь разные типы проблем. Веб-сервер возвращает коды состояния HTTP 4xx всякий раз, когда возникают ошибки при обработке запроса, полученного от браузера. Веб-сервер отправляет HTTP-ответ 400 Bad или Invalid Request, если он не может обработать запрос из клиентского браузера. Обычно это происходит из-за неверного синтаксиса запроса.

Для конечного пользователя получение этой ошибки при доступе к важному веб-сайту может быть довольно неприятным. Вы увидите коды ответа HTTP в браузере из-за сложной взаимосвязи между сервером веб-сайта, пользовательскими устройствами и сторонними службами. Таким образом, может быть сложно определить настоящую причину проблемы, даже если у вас есть контролируемая среда. Однако в большинстве ситуаций довольно легко разобраться в истинной первопричине.

Узнайте больше о том, что такое HTTP, о структуре HTTP-запроса и ответа.

Как исправить ошибку 400 Bad или Invalid Request HTTP?

Вот что вы можете сделать, чтобы исправить 400 неверных или недопустимых ошибок запроса.

A. Для обычных пользователей

Если вы обычный пользователь Интернета и получаете ошибку 400 в браузере, следуйте приведенным ниже решениям.

1. Обновите страницу.

Если у вас есть проблемы с доступом к странице, возможно, стоит попробовать обновить ее. В большинстве случаев HTTP-ошибка 400 Bad or Invalid Request является временной. В большинстве браузеров вы можете нажать клавишу F5 для обновления страницы. Если это не решит вашу проблему сразу, обновите страницу два или три раза, иногда может работать.

Обновить страницу в Chrome Chrome

2. Проверьте свой URL.

Если вы вводите URL-адрес в адресной строке, есть вероятность сделать орфографическую ошибку. Ошибка HTTP 400 Bad или Invalid Request может произойти из-за неправильного ввода URL. Также возможно, что в ссылке указан неверный URL или указан неправильный URL страницы, добавленной в закладки.

Проверьте адрес вручную и посмотрите, нет ли явных ошибок. Если вы не уверены в правильности URL-адреса страницы, попробуйте найти его в результатах поиска Google. У вас могут быть некоторые ключевые слова, которые могут быть связаны с веб-страницей. Выполните поиск по странице с использованием уникальных ключевых слов, чтобы повысить ваши шансы найти страницу.

3. Удалите файлы cookie и кеш.

Ошибка HTTP 400 Bad или Invalid Request может произойти, если ваши файлы cookie устарели или повреждены. Некоторые расширения браузера могут изменять файлы cookie и вызывать ошибки. Итак, в вашем браузере поврежденная версия кеша. Попробуйте очистить файлы cookie и кеш вашего сайта. После очистки кеша страницы могут загружаться немного медленнее, потому что вашему браузеру потребуется перестроить кеш с часто используемыми данными. Но это могло помочь решить проблему.

Помните, что при очистке файлов cookie вам может потребоваться повторно ввести данные для входа на все веб-сайты. Для очистки кеша и файлов cookie для каждого веб-браузера необходимы разные процедуры. Как правило, нажатие «Command + Shift + Delete» на Mac и «Control + Shift + Delete» в Windows будет работать в браузерах Chrome и Firefox.

Подробнее об очистке истории просмотров в популярных браузерах.

4. Очистить DNS

На вашем компьютере могут быть устаревшие записи DNS, и это может вызвать ошибки. Вы можете очистить DNS и проверить, решает ли это проблему с ошибкой 400 HTTP. Это легко сделать и не вызовет нежелательных проблем.

Узнайте подробную информацию о том, как очистить DNS в Windows и Mac.

5. Проверьте размер файла при загрузке.

Ошибка HTTP 400 Bad или Invalid Request может произойти, когда вы пытаетесь загрузить большой файл. Сначала проверьте разрешенный размер файла для загрузки. Если ваш файл больше, вы можете разделить его с помощью утилиты разделения файлов и загружать отдельные части файла.

6. Проверьте другие веб-сайты.

Если вы продолжаете получать ошибку HTTP 400 Bad или Invalid Request при попытке открыть веб-страницу, вам следует проверить, происходит ли это также с другими веб-сайтами. Если ошибка появляется снова, возможно, проблема с сетевыми устройствами на вашем компьютере. На компьютере с Windows запустите программу диагностики сети, чтобы устранить проблему с подключением. На Mac может потребоваться отключить и снова подключить устройство.

Вы также можете обратиться к поставщику услуг Интернета, чтобы узнать, могут ли они решить проблему.

7. Перезагрузите свои устройства.

Это может быть хит и промах. Однако перезагрузка сетевого оборудования и компьютера может помочь вам исправить ошибку HTTP 400 Bad или Invalid Request.

Б. Для разработчиков

Если вы разработчик, вы можете получить ошибку 400 HTTP при тестировании собственного приложения. Следуйте приведенным ниже параметрам, чтобы исправить ошибку.

8. Исправьте недопустимые заголовки HTTP.

Иногда проверка деталей HTTP-заголовка может дать подсказку об ошибке подключения. Вы можете просмотреть детали HTTP-заголовка с помощью одного из бесплатных инструментов в Интернете. Хотя это легко сделать для разработчиков, для не разработчиков это может быть довольно сложно.

9. Проверьте журналы сервера.

Веб-серверы обычно ведут журналы на стороне сервера для каждого запроса, отправляемого клиентом. Журнал может содержать такую информацию, как подключенное приложение, запрошенные страницы, IP-адрес и другую соответствующую информацию о запросах. Журналы сервера часто определяют причину сбоя и указывают статус обработки. Изучая журналы сервера, разработчики и администраторы могут легко определить причину проблем HTTP.

Если у вас нет доступа к файлам журнала сервера, запросите доступ у вашего хостинг-провайдера.

10. Сценарии отладки или код приложения

Если вы получаете сообщение об ошибке в пользовательских приложениях, это может быть связано с плохо написанным кодом в приложении. Разработчикам необходимо вручную отлаживать приложение и проверять журналы сервера для выявления потенциальных проблем.

Наличие хорошей системы управления ошибками может эффективно помочь разработчикам устранить ошибку HTTP 400 Bad или Invalid Request. Даже если ошибки случаются, вы можете обнаружить их автоматически. Например, аэродинамический тормоз — хорошая система мониторинга ошибок, предлагающая обновления в реальном времени. У него отличная панель инструментов, которая предлагает круглосуточные обновления о состоянии вашего веб-приложения. С помощью настраиваемого фильтра ошибок вы можете получать обновления о наиболее важных ошибках.

Заключение

Как объяснялось выше, ошибка 400 происходит из-за отправки неверного запроса на сервер. Это могло быть связано с загрузкой файла или повреждением файлов cookie браузера. Следуйте приведенным выше решениям, и мы надеемся, что одно из них поможет вам решить проблему. Если проблема не исчезнет, это также может быть связано с дополнительными сторонними факторами между вашим браузером и сервером. Подождите некоторое время и попробуйте позже получить доступ к веб-страницам.

В пользовательских приложениях разработчики могут выполнять пошаговый процесс отладки, чтобы найти реальную проблему.

HTTP header 400 bad request response

I’m trying to test writing correct HTTP headers to understand the syntax. Here I’m trying to PUT some text into httpbin.org/put and I expect the response body content to be the same.

However I’m getting the following bad request 400 response:

What syntactical errors have I done? NOTE: newlines are \r\n not \n in the request.

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Apparently the correct syntax goes like this for PUT:

I believe I didn’t say much on how I connected to httpbin.org; it was via sockets in C. So the connection was already established before sending the header + message.

You miss the destination url following the PUT verb, the first line must be:

This will probably also fail, you need one of their handler urls so they know what to reply with:

The general form of the first line, or Request Line, in an HTTP request is as follows:

Where for your example, the method is PUT. Including an absolute URL (so, starting with http:// or https:// is only necessary when connecting to a proxy, because the proxy will then attempt to retrieve that URL, rather than attempt to serve a local resource (as found by the path component).

Hope that helped. Consult the HTTP 1.1 RFC (2616), section 5.1 for more information and the official definitions.

request failed with status code 400

this is my serverrender.js code

this is my srver.js code

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

You should add a catch to the get call:

You need to enclose the opening parentheses of the config variable.

Response code 400 or 403 for POST Restful APIs

I am designing a POST Restful API, where I have a situation that I have to authorize a user based upon one of the element provided in the request body. For eg.

So the user making POST request should be authorized to work on division 1. I cannot authorize the user without getting request body.

Also is it okay to do something like :

[EDIT] we preferred not to use 422 error code

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

When in doubt, just take a look at the RFC

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.

422 Unprocessable Entity (WebDAV; RFC 4918)

The request was well-formed but was unable to be followed due to semantic errors.

That is what I usually use in situations like this.

Again, I don’t think either 400 or 403 make a good case here. Specifically for this situation, 401 exists

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.

Error: Request failed with status code 400. Differences between sending in POSTMAN and in the application

In POSTMAN it works:

In the function submit method POST, when the form is submit, it does not work. I have error:

Error: Request failed with status code 400 at createError (createError.js?2d83) at settle (settle.js?467f) at XMLHttpRequest.handleLoad (xhr.js?b50d)

In tab Network in response I have:

Login

What are the differences between sending in POSTMAN and in the application? Contents of the body convert to a string?

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Axios handles error differently.

To find out what really is the issue.

You should use error.request to check if the request you made has error

and use error.response to get the error feedback from the server

Localhost:3000/api/products 404 Error You did not create res.get(«/api/products») on server.js or you did not set the proxy. check below for proxy setting.

Proxy error: could not proxy request /api/products Check this:

400 vs 422 for Client Error Request

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request
message framing, or deceptive request routing).

I did find this statement in the Appendix B of the rfc 7231:

The 400 (Bad Request) status code has been relaxed so that it isn’t
limited to syntax errors. (Section 6.5.1)

Does this mean that I can consider any type of client error a bad request? Would it be better to use 400 for client requests and just specify a more specific error in the message?

The 422 (Unprocessable Entity) status code means the server
understands the content type of the request entity (hence a
415(Unsupported Media Type) status code is inappropriate), and the
syntax of the request entity is correct (thus a 400 (Bad Request)
status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML
request body contains well-formed (i.e., syntactically correct), but
semantically erroneous, XML instructions.

Can I use this webDAV extension codes to handle my http requests? In the case of 422, can I use it even though it’s not in the core http codes.

Should I use 400 or 422 for my client error?

Here are the possible client error I have in mind:

Any informative response will be highly appreciated. Thanks a lot, guys!

Update: I checked google api errors and they are not using 422. On the other hand, Twitter uses 422. I’m more confused than ever >. Follow

Как исправить ошибку 400 Bad или Invalid Request HTTP?

Вот что вы можете сделать, чтобы исправить 400 неверных или недопустимых ошибок запроса.

A. Для обычных пользователей

Если вы обычный пользователь Интернета и получаете ошибку 400 в браузере, следуйте приведенным ниже решениям.

1 Обновите страницу

Если у вас есть проблемы с доступом к странице, возможно, стоит попробовать обновить ее. В большинстве случаев HTTP-ошибка 400 Bad или Invalid Request является временной. В большинстве браузеров вы можете нажать клавишу F5 для обновления страницы. Если это не решит вашу проблему немедленно, иногда может сработать обновление страницы два или три раза.

Обновить страницу в Chrome Chrome

2 Проверьте свой URL

Если вы вводите URL-адрес в адресной строке, есть вероятность сделать орфографическую ошибку. Ошибка HTTP 400 Bad или Invalid Request может произойти из-за неправильного ввода URL. Также возможно, что в ссылке указан неверный URL-адрес или неверный URL-адрес страницы, добавленной в закладки.

3 Удаление файлов cookie и кеша

Ошибка HTTP 400 Bad или Invalid Request может произойти, если ваши файлы cookie устарели или повреждены. Некоторые расширения браузера могут изменять файлы cookie и вызывать ошибки. Итак, в вашем браузере повреждена версия кеша. Попробуйте очистить файлы cookie и кеш вашего сайта. После очистки кеша страницы могут загружаться немного медленнее, потому что вашему браузеру потребуется перестроить кеш с часто используемыми данными. Но это могло помочь решить проблему.

Помните, что при очистке файлов cookie вам может потребоваться повторно ввести данные для входа на все веб-сайты. Вам нужны разные процедуры для очистки кеша и файлов cookie для каждого веб-браузера. Как правило, нажатие «Command + Shift + Delete» на Mac и «Control + Shift + Delete» в Windows работает в браузерах Chrome и Firefox.

4 Очистить DNS

На вашем компьютере могут быть устаревшие записи DNS, и это может вызвать ошибки. Вы можете очистить DNS и проверить, решает ли это проблему с ошибкой 400 HTTP. Это легко сделать, и это не вызовет нежелательных проблем.

5 Проверьте размер файла при загрузке

Ошибка HTTP 400 Bad или Invalid Request может произойти при попытке загрузить большой файл. Сначала проверьте разрешенный размер файла для загрузки. Если ваш файл больше, вы можете разделить его с помощью утилиты разделения файлов и загружать части файла по отдельности.

6 Проверьте другие веб-сайты

Если вы продолжаете получать ошибку HTTP 400 Bad или Invalid Request при попытке открыть веб-страницу, вам следует проверить, происходит ли это также с другими веб-сайтами. Если ошибка появляется снова, возможно, проблема с сетевыми устройствами на вашем компьютере. На компьютере под управлением Windows запустите программу диагностики сети, чтобы устранить проблему с подключением. На Mac может потребоваться отключить и снова подключить устройство.

Вы также можете обратиться к поставщику услуг Интернета, чтобы узнать, могут ли они решить проблему.

7 Перезагрузите свои устройства

Б. Для разработчиков

8 Исправить неверные заголовки HTTP

Иногда проверка деталей HTTP-заголовка может дать подсказку об ошибке подключения. Вы можете просмотреть детали HTTP-заголовка с помощью одного из бесплатных инструментов в Интернете. Хотя это легко сделать для разработчиков, для не-разработчиков это может быть довольно сложно.

9 Проверка журналов сервера

Если у вас нет доступа к файлам журнала сервера, запросите доступ у вашего хостинг-провайдера.

10 сценариев отладки или код приложения

Наличие хорошей системы управления ошибками может эффективно помочь разработчикам устранить ошибку HTTP 400 Bad или Invalid Request. Даже если ошибки случаются, вы можете обнаружить их автоматически. Например, Airbrake – хорошая система мониторинга ошибок, предлагающая обновления в режиме реального времени. У него отличная панель инструментов, которая предлагает круглосуточные обновления о состоянии вашего веб-приложения. С помощью настраиваемого фильтра ошибок вы можете получать обновления о наиболее важных ошибках.

Заключение

Как объяснялось выше, ошибка 400 происходит из-за отправки неверного запроса на сервер. Это может быть связано с загрузкой файла или повреждением файлов cookie браузера. Следуйте приведенным выше решениям, и мы надеемся, что одно из них поможет вам решить проблему. Если проблема не исчезнет, это также может быть связано с дополнительными сторонними факторами между вашим браузером и сервером. Подождите некоторое время и попробуйте позже получить доступ к веб-страницам.

В пользовательских приложениях разработчики могут выполнять пошаговую отладку, чтобы найти реальную проблему.

Status Code 400

An HTTP (Hypertext Transfer Protocol Bad) State code 400 represents a user error. Whenever any user sends an invalid request to the server, the server immediately reports it and generates an HTTP based 400 bad request error. This error usually occurs if the user has entered an incorrect URL.

In the broad majority of likely situations, the status code 400 error occurs due to a client-side problem caused by the submitted request to the server or local caching causes. Hence, in this tutorial, we will cover various easy methods that anyone can implement even if the user is not tech-savvy. Following the given methods, you should be successfully able to make your website working!

What is a 400 bad Request error?

Status Code 400 or 400 Bad Request, or 400 error or HTTP error 400, is recognized by the server as a general user error. The server throws the 400 bad error if the server decides that the resulting error doesn’t come under any other status code classifications.

The 400 status code (Bad Request) represents that the server cannot process the request due to some user error. In return for an invalid request, the server should dispense the specific 4xx status code in the case of a failed request.

Common Causes of 400 error

A 400 Bad Request error is mostly the consequence of typing the incorrect URL in the browser window or making errors in an address link while linking it from a web page to another.

1. URL String Syntax Error

The primary reason for the HTTP error 400 to occur is an incorrectly typed URL (Uniform Resource Locator), deformed syntax, or a URL that contains some illegal characters.

Though the user can mistakenly type the wrong URL, it can sometimes happen if the URL encoding has been performed incorrectly. The below-given link is an example of an incorrect URL that the server won’t process, and therefore, it will trigger a 400 HTTP error.

2. Corrupted Browser Cache & Cookies

URL typo error is not the only case where the server triggers the 400 bad error. Even if the passed URL is 100% accurate, the server can still throw a 400 Bad Request error because it detects the presence of any corrupted files in the browser cache memory or other issues such as expired or damaged cookies.

The user can also encounter a 400 Bad Request error if he/she tries to gain access to their WordPress admin area after some time of their last log-in session. The reason why it occurred because the process following which the cookie was managing the login authentication information may have gotten expired, and it cannot further authenticate the same valid user with admin rights. And it eventually results in the connection being declined and therefore passes 400 Bad Request error.

3. DNS Lookup Cache

The 400 Bad Request can occur if the local DNS data stored is not in sync with registered DNS (Domain Name server) data. All the domain names available on the internet are the art of IP address. You can compare the IP address of your phone number as it connects to a particular «calling number» you wish to dial.

4. File Size Too Large

A 400 Bad Request can also trigger if the files uploaded by the user on a website are too heavy for the upload request to be met. This is strictly associated with the server’s file size limit and will change based on its setup.

5. Generic Server Error

The 400 bad request error can also occur if there is any technical issue on the server-side. Though, a 400 status code will display a generic problem with the server, server or network glitch, or any other undefined volatile issues.

Suppose it triggers when the user tries to connect to a third-party website, in that the user cannot control it. At that time, he/she can try to refresh the browser and monitor at frequent intervals whether the website developers have resolved the issue or not. Just in case you want to confirm whether the specific error is a server-side issue or not, try to load the website on various browsers, or you can also test it on a different machine/device to eliminate the system-specific problems.

If the same issue occurs with other browsers, systems are also confirmed to be a server-side problem. If the site content is important for you, you directly communicate to the website owner and give all the details related to Operating System, browser, system, and versions you were using when you experienced the 400 bad error issue.

How to fix 400 Errors

The various ways to fix the bad 400 errors are explained below:

1. Check the Submitted URL

One of the most common reasons for the 400 Bad Request error is the obvious URL string itself. One can easily make mistakes by manually typing unwanted characters in the URL in the web browser.

Re-check the spelling of the domain name or the particular web page you want to access and make sure that they are typed accurately and are separated with forwarding slashes. If the URL includes any special characters, make sure they are encoded properly with valid URL characters.

If you find it hard to check the URL spelling and encoding process repeatedly, you can opt for the online URL encoder/decoder. It is very useful for long URLs and less error-prone. These kinds of software help the user to identify various illegal characters in the URL automatically.

Once you have entered the correct URL, it’s time to run it again in the browser. Still, if you face the 400 Bad Request error, try with other fixing methods given below.

2. Clear Browser Cache

While accessing specific website content, the user receives a 400 Bad Request error if any website files stored locally have been corrupted.

It consists of all sorts of files that a website demands for its proper functioning, unlike:

Whenever any user visits any website, all the above files are stored locally on your computer’s browser. Therefore to fix this problem, one should clear the browser’s cache memory. Follow the below-given steps to clear the computer cache:

Note: Google provides you the option to delete only the recent files for a particular time range with the help of the Time range dropdown. However, to ensure all possibly corrupted files are eliminated, we suggest removing all stored files locally by selecting the All-time option.

3. Clear Browser Cookies

If you are still facing the 400 error even after clearing your browser cache, in that case, your browser cookies are also corrupted. Whenever you open any website on your browser, it uses different cookies. If any one of the used cookies gets expired or corrupted, then it can trigger the 400 Bad Request error.

To clear your cookies in web browser (Chrome in our case) follow the below given steps:

4. File Upload Exceeds Server Limit

While uploading a file, we often forget about the server size limit and exceed its maximum limit. Eventually, you confront a 400 Bad Request error.

Try to upload a file again, and this time upload a smaller file. If it gets uploaded successfully, then the likely error occurred because the initial file was too large, and before uploading the file again, either you need to trim the file size or need to find some way.

5. Clear DNS Cache

The 400 Bad request can be triggered if the DNS data stored locally gets corrupted or out-of-date.

Note: The local DNS data are not stored by the browser but on the OS (operating system).

6. eactivate Browser Extensions

Today, we install various extensions to our browser. Some extensions might affect your website cookies which could trigger the 400 bad request error. To find out the real culprit, temporarily disable them and check whether it makes a difference by running the website again.

Request failed with status code 400

This forum is closed. Thank you for your contributions.

Answered by:

Question

Here is the background. I deployed a LightSwitch 2013 web applicaiton to my local webserver using the publishing tool in Visual Studio. The site works great with no problems. I am able to load records from the external SQL Server. However when I deploy the exact same published package to our UAT web server I am having an issue. THere is an error statement where the data records are displayed that reads «Request failed with status code ‘400’ and status text ‘Bad Request’.» I turned on the Failed Request tracing for the application and found 2 logs. Here are the tracing logs:

The second log is identical to this log with the exception of the service being used.

I compared the IIS configs on the UAT server and my Dev server. The only differences that I could find are some missing assemblies on the UAT server. But I don’t really think this is the issue. The missing assemblies are these 3:

Microsoft.VisualStudio.Web.PageInspector.Loader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a System.Web.WebPages.Deployment, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 System.Web.WebPages.Deployment, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

The application pools have identical configurations.

One other thing. I created a very basic Lightswitch application to display some database records to test the database connection. I deployed this to the UAT webserver and this application works perfectly. This app uses the same database as my real app.

Any help would be really appreciated. I am at a loss as to what the problem is. Thanks!

HTTP API Errors

We want your feedback

Common HTTP error codes used in the commercetools Composable Commerce APIs and the meaning of the error codes.

For details about the structure and application-specific error-codes of a specific commercetools Composable Commerce API, consult the documentation dedicated to that API.

Common HTTP error codes

400 Bad Request

A 400 is the most commonly expected error response and indicates that a request failed due to providing bad input. Bad input can be a malformed request body, missing required parameters, wrongly typed or malformed parameters or a parameter that references another resource that does not exist. Clients need to resolve the problems mentioned in the response before re-sending the request.

401 Unauthorized

A 401 indicates that the request is not properly authenticated.

403 Forbidden

A 403 indicates that the authenticated client is not allowed to perform the request.

404 Not Found

A 404 indicates that the addressed resource was not found / does not exist.

409 Conflict

A 409 indicates that the current version of the resource targeted by the request (with the intention to modify or delete it) is different from that provided in the request. In response to this, the client will usually want to request the newest version of the resource to see what has been changed and decide what changes to apply to the newest version.

A 409 Conflict indicates a concurrent modification and usually occurs on a versioned resource, which requires the client to provide the version of the resource to perform a change.

Whenever possible the HTTP response body contains the currentVersion field (optional) like this:

500 Internal Server Error

A 500 indicates that a request failed due to a server-side problem that needs to be resolved before subsequent requests can succeed. It either indicates a temporary unavailability or permanent server-side problem that needs to be reported and resolved.

502 Bad Gateway

A 502 indicates that a request failed due to a server-side problem caused by scaling infrastructure resources. The client application should retry the request with exponential backoff up to a point where further delay is unacceptable.

Error responses

The general structure of error responses from the API is as follows:

The error response always has the following fields:

Some errors have additional fields beside code and message and are documented appropriately.

The following sections describe the possible errors in the following way:

OAuth related errors

Errors related to authentication and authorization also conform to the OAuth 2.0 specification

Also note that error codes defined by the OAuth spec are not written in camelCase.

Errors from an API Extension

API Extensions can validate API calls and reject updates resulting in a 400 Bad Request response. API Extensions also have Error Cases.

When an API Extension is involved in the error, the errorByExtension field is added to the error response. The errorByExtension field contains the id and (if set) the key of the API extension. If the API Extension returns localizedMessage or the extensionExtraInfo fields in a Validation Error, they are also added to the error response.

General

500 Internal Server Error

The following general error codes can appear in responses with the HTTP status code 500 :

503 Service Unavailable

The following general error codes can appear in responses with the HTTP status code 503 :

OverCapacity
The service is having trouble handling the load.
The client application should retry the request with exponential backoff up to a point where further delay is unacceptable.

PendingOperation
A previous conflicting operation is still pending and needs to finish before the request can succeed.
The client application should retry the request with exponential backoff up to a point where further delay is unacceptable.
If these errors persist, they should be reported on the Support Portal

404 Not Found

The following general error codes can appear in responses with the HTTP status code 404 :

400 Bad Request

The following general error codes can appear in responses with the HTTP status code 400 :

AnonymousIdAlreadyInUse
The anonymous ID is already in use by another resource.
The client application should choose another anonymous ID or retreive an automatically generated one.

DuplicateField
A value for a field conflicts with an existing duplicate value.
Extra fields:

DuplicateFieldWithConflictingResource
A value for a field conflicts with an existing duplicate value stored in a particular resource.
Extra fields:

FeatureRemoved
The resource requested was removed.
The client application should use the feature recommended by the error message instead.

InvalidInput
Invalid input has been sent to the service.
The client application should validate the input according to the constraints described in the error message before sending the request.

InvalidJsonInput
Invalid JSON input has been sent to the service. Either the JSON is syntactically not correct, or the JSON does not conform to the expected shape (for example is missing a required field).
The client application should validate the input according to the constraints described in the error message before sending the request.

InvalidOperation
The resources involved in the request are not in a valid state for the operation. The client application should validate the constraints described in the error message before sending the request.

InvalidField
A field has an invalid value.
Extra fields:

InternalConstraintViolated
The discount code specified was never applied and cannot be updated.

MaxResourceLimitExceeded
No more resources of the type in this request can be created. Limits configuration should be adjusted for this resource before sending the request again.
Extra fields:

ObjectNotFound
The requested resource was not found.

ReferenceExists
A resource cannot be deleted because it is referenced by something else.

ReferencedResourceNotFound
A resource referenced by a Reference or a ResourceIdentifier could not be found.
Extra fields:

RequiredField
A required field is missing a value.
Extra fields:

ResourceSizeLimitExceeded
The resource exceeds the maximum allowed size of 16 MB.

SemanticError
The predicate is not semantically correct.

SyntaxError
The search query or predicate does not have correct syntax.

QueryTimedOut
The query timed out. If your query constantly times out, please check that it follows the performance best practices.

409 Conflict

The following general error codes can appear in responses with the HTTP status code 409 :

Extension error responses

The following error codes are returned when an API Extension triggered during an API request did not respond successfully.

400 Extension Predicate Evaluation Failed

502 Extension Bad Response

502 Extension Update Actions Failed

504 Extension No Response

External OAuth error responses

The following error code is returned when an External OAuth Introspection endpoint triggered during an API request did not respond successfully.

502 or 504 External OAuth Failed

Products

400 Bad Request

The following product-specific error codes can appear in responses with the HTTP status code 400 :

DuplicatePriceScope
A given price scope conflicts with an existing one. Every price of a product variant must have a distinct combination of currency, country, customer group, channel, valid from and valid until. These six properties constitute the scope of a price.
Extra fields:

DuplicateVariantValues
A given combination of variant values conflicts with an existing one. Every product variant must have a distinct combination of SKU, prices, and custom attribute values.
Extra fields:

DuplicateAttributeValue
The Unique AttributeConstraint was violated.
Extra fields:

DuplicateAttributeValues
The CombinationUnique AttributeConstraint was violated.
Extra fields:

Product Types

400 Bad Request

The following product type-specific error codes can appear in responses with the HTTP status code 400 :

AttributeDefinitionAlreadyExists
A given AttributeDefinition name conflicts with an already defined attribute.
Extra fields:

AttributeDefinitionTypeConflict
A given AttributeDefinition name already exists on another product type with a different type.
Extra fields:

DuplicateEnumValues
A given enum or lenum contains duplicate keys.
Extra field:

EnumKeyAlreadyExists
A given enum or lenum contains key that already exists.
Extra fields:

EnumKeyDoesNotExist
The enum or lenum already contains a value with the given key.
Extra fields:

AttributeNameDoesNotExist
An AttributeDefinition for the given attribute name does not exist.
Extra fields:

EnumValuesMustMatch
When reordering enum or lenum values all existent values must be passed

EnumValueIsUsed
When removing an EnumValue from a required attribute, but the EnumValue is still used by a product.

Orders

400 Bad Request

The following order-specific error codes can appear in responses to Create Order from Cart requests with the HTTP status code 400 :

OutOfStock
Some of the ordered line items are out of stock at the time of placing the order.
Extra fields:

PriceChanged
The price, tax, or shipping of some line items changed since the items were added to the cart.
Extra fields:

InvalidItemShippingDetails
A line item or custom line item has one or more shipping addresses set, but the quantity of that item does not match the sum of the quantities in its shipping details.
Extra fields:

MatchingPriceNotFound
The product variant does not have a price according to the Product’s priceMode value for a selected currency and/or country, customer group or channel.
Extra fields:

Error: Request failed with status code 400 when expo buidl

When you build expo you can face an error: at createError (/usr/local/lib/node_modules/turtle-cli/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/turtle-cli/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/turtle-cli/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:322:22) at IncomingMessage.EventEmitter.emit (domain.js:482:12) at endReadableNT (_stream_readable.js:1187:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) <

1 Answer 1

It seems that project is not published to Expo website.

You have to publish project first 🙂

Not the answer you’re looking for? Browse other questions tagged build expo or ask your own question.

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Error: Request failed with status code 400 [expo-cli]

TL; DR

Logout from expo-cli and log in again

Intro

Yesterday I had an issue with expo-cli. I was testing some stuff on my phone and everything was great. I have used expo start to preview. After a few moments I kept expo-cli running and put my computer to sleep. A few hours later I’ve tried to preview the project following the same steps, which threw the error shown here

The issue seemed to be caused by axios. I have tried everything. I mean everything.
Removed all api calls, no help.
Reinstall expo, no help.
Reinstall expo-cli, no help.

I have almost started pulling my hair and then out of thin air I have come up with this idea which is explained down below.

I am not sure but I think this error was caused because I have left the expo-cli open.

I won’t dive deep into the details here because I am mostly certain that this error is because of expo-cli itself.

Well, I have found some solutions for the issue but non of them worked for me.

Here’s how I solved the issue

Solution

Just log out from expo-cli and log in again. That’s just it

HTTP 400 (bad request) for logical error, not malformed request syntax

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

There seems to be a general practice among a few HTTP-based APIs these days to use 400 to mean a logical rather than a syntax error with a request. My guess is that APIs are doing this to distinguish between 400 (client-induced) and 500 (server-induced). Is it acceptable or incorrect to use 400 to indicate non-syntactic errors? If it is acceptable, is there an annotated reference on RFC 2616 that provides more insight into the intended use of 400?

8 Answers 8

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Status 422 (RFC 4918, Section 11.2) comes to mind:

The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.

As of this time, the latest draft of the HTTPbis specification, which is intended to replace and make RFC 2616 obsolete, states:

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.

This definition, while of course still subject to change, ratifies the widely used practice of responding to logical errors with a 400.

HTTPbis will address the phrasing of 400 Bad Request so that it covers logical errors as well. So 400 will incorporate 422.

From https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-p2-semantics-18#section-7.4.1
«The server cannot or will not process the request, due to a client error (e.g., malformed syntax)»

Even though, I have been using 400 to represent logical errors also, I have to say that returning 400 is wrong in this case because of the way the spec reads. Here is why i think so, the logical error could be that a relationship with another entity was failing or not satisfied and making changes to the other entity could cause the same exact to pass later. Like trying to (completely hypothetical) add an employee as a member of a department when that employee does not exist (logical error). Adding employee as member request could fail because employee does not exist. But the same exact request could pass after the employee has been added to the system.

It could be argued that having incorrect data in your request is a syntax error, even if your actual request at the HTTP level (request line, headers etc) is syntactically valid.

I don’t know of any official references to back this up though, as usual it seems to be down to interpreting RFC 2616.

Update: Note the revised wording in RFC 7231 §6.5.1:

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

seems to support this argument more than the now obsoleted RFC 2616 §10.4.1 which said just:

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

In English syntax rules prescribe certain relationships between parts of speech. For instance «Bob marries Mary» is syntactically correct, because it follows the pattern . Whereas «Bob marriage Mary» would be syntactically incorrect, .

The syntax of a simple URLis < protocol + : + // + server + : + port >. According to this «http://www.google.com:80» is syntactically correct.

But what about «abc://www.google.com:80»? It seems to follow the exact same pattern. But really it is a syntax error. Why? Because ‘abc’ is not a DEFINED protocol.

The point is that determining whether or not we have a 400 situation requires more than parsing the characters and spaces and delimiters. It must also recognize what are the valid «parts of speech».

This is difficult.

I think we should;

Return 4xx errors only when the client has the power to make a change to the request, headers or body, that will result in the request succeeding with the same intent.

Return error range codes when the expected mutation has not occured, i.e. a DELETE didn’t happen or a PUT didn’t change anything. However, a POST is more interesting because the spec says it should be used to either create resources at a new location, or just process a payload.

Using the example in Vish’s answer, if the request intends to add employee Priya to a department Marketing but Priya wasn’t found or her account is archived, then this is an application error.

The request worked fine, it got to your application rules, the client did everything properly, the ETags matched etc. etc.

Because we’re using HTTP we must respond based on the effect of the request on the state of the resource. And that depends on your API design.

Perhaps you designed this.

Returning a success code would indicate that the «replacement» of the resource worked; a GET on the resource would reflect your changes, but it wouldn’t.

So now you have to choose a suitable negative HTTP code, and that’s the tricky part, since the codes are strongly intended for the HTTP protocol, not your application.

When I read the official HTTP codes, these two look suitable.

The 409 (Conflict) status code indicates that the request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request. The server SHOULD generate a payload that includes enough information for a user to recognize the source of the conflict.

The 500 (Internal Server Error) status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

Though we’ve traditionally considered the 500 to be like an unhandled exception :-/

I don’t think its unreasonable to invent your own status code so long as its consistently applied and designed.

This design is easier to deal with.

Then you could design your API to always succeed in creating the instruction, it returns 201 Created and a Location header and any problems with the instruction are held within that new resource.

A POST is more like that last PUT to a new location. A POST allows for any kind of server processing of a message, which opens up designs that say something like «The action successfully failed.»

Probably you already wrote an API that does this, a website. You POST the payment form and it was successfully rejected because the credit card number was wrong.

With a POST, whether you return 200 or 201 along with your rejection message depends on whether a new resource was created and is available to GET at another location, or not.

With that all said, I’d be inclined to design APIs that need fewer PUTs, perhaps just updating data fields, and actions and stuff that invokes rules and processing or just have a higher chance of expected failures, can be designed to POST an instruction form.

Как исправить ошибку 400 – подробная инструкция по решению проблемы

В наше время тяжело представить себе человека, который не пользуется услугами интернета. Кто-то черпает на его просторах необходимую информацию, кто-то наслаждается любимыми играми, а кто-то и вовсе — занимается удаленной работой.

Каждый из них, хоть раз, но сталкивался с тем, что на запрос определенной интернет страницы появлялось непонятное сообщение — «400 — Bad Request».

Что означает данное сообщение и почему возникает — обычный пользователь об этом не имеет не малейшего представления.

В нашей статье мы постараемся разобраться — что представляет собой 400 bad request как исправить и как в дальнейшем избежать возникновения подобной ситуации.

В компьютерном мире ошибка 400 (неверный запрос) возникает в том случае, если сервер не в состоянии обработать клиентский запрос. Подобное происходит вследствие неправильного синтаксиса, который способствует созданию необходимых взаимоотношений между различными веб-сервисами, а также клиентом и веб-приложениями.

Из-за этого довольно тяжело разобраться с причиной появления данной проблемы даже в контролируемой среде разработки.

На чьей стороне возникла ошибка

Для тех, кто еще не знает — если код имеет категорию 4хх — это данные ответа http, а ошибки с такими цифровыми значениями возникают на стороне клиента.

Под клиентом следует понимать как браузер, так и устройство, с помощью которого осуществляется доступ к приложению.

По своей сути, возникновение подобной ошибки может означать, что клиентское устройство отправило по какой-либо причине неверный запрос. Это может быть не только неправильно сформированный запрос, но и попытка провести загрузку слишком большого файла. Сюда же вполне можно отнести и неправильно сформированные заголовки http, которые также вызывают ошибку с кодом 4хх.

Рис.2 Сервер не смог распознать запрос.

Далее мы постараемся детально рассмотреть наиболее распространенные сценарии возникновения ошибки, а также возможные варианты ее решения.

Помните, что в данном случае объектом, генерирующим ошибку 400-Bad Request, может быть как клиент, так и запрашиваемый сервер.

Диагностирование ошибки

Возникновение ошибки неверного запроса может быть вызвано одной из ниже перечисленных причин:

Решение проблемы с клиентской стороной

Как бы то ни было, а наиболее правильным решением буде поиск и исправление неисправности клиентских устройств и приложений.

Первым делом стоит проверить правильность запрашиваемого URL.

Зачастую ошибка кроется в его некорректном вводе.

Рис.3 Пример отображения доменного имени и URL запрашиваемого сайта.

Не забывайте, что доменные имена — как бы вы их не набрали — ни в коей мере не повлияют на правильную работу ссылки.

К примеру, internet-company winter group.ru и inTErnet-COmpany grouP.ru будут работать абсолютно одинаково. Зато все, что касается URL — информация, идущая после доменного имени — чувствительны к регистру и должны иметь верное написание. В случае, когда URL содержит неправильные символы — сервер отвечает на запрос отображением кода возникшей ошибки.

Очистка файлов cookie

Наличие на локальном сервере идентичных или некорректных куки-файлов также является причиной появления ошибки 400 Bad Request.

Эти файлы представляют собой небольшое количество данных, которыми пользуются различные сайты для того, чтобы запомнить конкретное устройство или браузер, с которого осуществлялся запрос.

Благодаря этому все последующие визиты на такой сайт происходят намного быстрее, чем в первый раз.

Наличие таких куки-файлов создает удобство для пользователя, но может быть и причиной конфликта с токеном сессии другого пользователя. В данном случае одному из вас, а быть может и обоим одновременно, сервер выдаст ошибку 4хх.

Рис.4 Окно удаление файлов cookie.

При удалении cookie не следует полностью избавляться от всех имеющихся — достаточно удалить те из них, которые соответствуют определенному доменному имени.

Однако, если вы не имеете представление в выборочном удалении — будет наиболее правильным полностью очистить браузер от файлов cookie.

Каждый браузер располагает своей схемой очистки, однако, все они в чем-то схожи между собой.

Очистка кэш памяти браузера Chrome

После этих действий все сохраненные куки будут удалены из вашего браузера.

Загрузка файлов с меньшим объемом

Если вы загружаете определенный файл и получаете ошибку неверного запроса — возможно причина ее возникновения кроется в слишком большом объеме.

Попробуйте загрузить файл меньшего размера, чтобы удостовериться в корректной работе приложения.

Откат последних изменений

Если перед появлением ошибки 400 Bad Request вы делали обновление системы управления клиентом — решением проблемы может быть откат к ранее установленной версии.

Кроме этого, можно осуществить откат и обновленных расширений и модулей, так как они тоже могут являться причиной появления неприятной ситуации.

Удаление новых расширений и модулей

Некоторые расширения имеют неприятную особенность — изменять в базе данных таблицы и записи, которые им не принадлежат.

В этом случае придется удалить последние установленные расширения, а затем вручную очистить базу данных от их последствий.

Переустановка программы Windows Operating System

Неправильная работа данной программы может послужить причиной возникновения Bad Request. Для решения вопроса следует произвести ее переустановку.

Рассмотрим удаление данной программы на примере ОС Windows 7.

Для этого выполните следующие действия:

Рис.5 Окно «Программы и компоненты».

После удаления вам понадобится заново установить эту программу, воспользовавшись инструкцией Microsoft Corporation.

Выявление и удаление вредоносов

Еще одной причиной, способной вызвать ошибку 400, является заражение вашего компьютера различными вредоносными программами.

Такие программы могут изменить либо полностью удалить файлы состояния браузера.

Кроме того, некоторые компоненты вредоносной программы могут сами служить причиной возникновения ошибки.

Чтобы иметь возможность защиты от подобного рода программ — установите на компьютер соответствующее приложение. Одним из лучших является Emsisoft Anti-Malware. Это приложение не только защищает, но и гарантированно удаляет любое вредоносное ПО.

Рис.6 Программа Emsisoft Anti-Malware.

Обновление драйверов

Как ни странно, но устаревшие или некорректно работающие драйвера тоже способны создать подобную проблему, поэтому старайтесь как можно чаще проверять их работоспособность и вовремя проводить обновление.

Вручную проверять и обновлять каждый драйвер слишком долго, поэтому проще всего установить на компьютер такую программу, как DriverDoc, которая полностью избавит вас от этой рутинной работы.

Обновление Windows

Корпорация Microsoft не прекращает работу, связанную с обновлением и улучшением системных файлов своих операционных систем.

В некоторых случаях необходимо просто обновить коды состояний браузера и ошибка Bad Request исчезнет сама собой.

Рис.7 Окно обновления Windows.

Для этого понадобится воспользоваться кнопкой «Начать» и ввести в строку поискового запроса «update» (обновление), после чего нажать на клавишу Enter.

В этом случае откроется диалоговое окно обновления ОС, в котором будут отображаться все доступные пакеты (если такие имеются).

Если ни один из вариантов не помог избавиться от возникшей проблемы — обратитесь к специалистам.

Видеоролик на тему решения проблемы 400 Bad Request:

A Complete Guide and List of HTTP Status Codes

HTTP status codes are like short notes from a server that get tacked onto a web page. They’re not actually part of the site’s content. Instead, they’re messages from the server letting you know how things went when it received the request to view a certain page.

These kinds of messages are returned every time your browser interacts with a server, even if you don’t see them. If you’re a website owner or developer, understanding HTTP status codes is critical. When they do show up, HTTP status codes are an invaluable tool for diagnosing and fixing website configuration errors.

This article introduces several server status and error codes, and explains what they reveal about what’s happening on the server behind the scenes.

Prefer to watch the video version?

What Are HTTP Status Codes?

Every time you click on a link or type in a URL and press Enter, your browser sends a request to the webserver for the site you’re trying to access. The server receives and processes the request, and then sends back the relevant resources along with an HTTP header.

HTTP status codes are delivered to your browser in the HTTP header. While status codes are returned every single time your browser requests a web page or resource, most of the time you don’t see them.

It’s usually only when something goes wrong that you might see one displayed in your browser. This is the server’s way of saying: “Something isn’t right. Here’s a code that explains what went wrong.”

Google 404 HTTP status code

If you want to see the status codes that your browser doesn’t normally show you, there are many different tools that make it easy. Browser extensions are available for developer-friendly platforms such as Chrome and Firefox, and there are many web-based header fetching tools like Web Sniffer.

To see HTTP status codes with one of these tools, look for the line appearing near the top of the report that says “Status: HTTP/1.1”. This will be followed by the status code that was returned by the server.

Understanding HTTP Status Code Classes

HTTP status codes are divided into 5 “classes”. These are groupings of responses that have similar or related meanings. Knowing what they are can help you quickly determine the general substance of a status code before you go about looking up its specific meaning.

The five classes include:

Within each of these classes, a variety of server codes exist and may be returned by the server. Each individual code has a specific and unique meaning, which we’ll cover in the more comprehensive list below.

Why HTTP Status Codes and Errors Matter for Search Engine Optimization (SEO)

Search engine bots see HTTP status codes while they’re crawling your site. In some cases, these messages can influence if and how your pages get indexed, as well as how search engines perceive the health of your site.

Sign Up For the Newsletter

Want to know how we increased our traffic over 1000%?

Join 20,000+ others who get our weekly newsletter with insider WordPress tips!

Generally speaking, 100- and 200-level HTTP status codes won’t have much impact on your SEO. They signal that everything is working as it should on your site, and enable search engine bots to continue on their way. However, they aren’t going to boost your rankings either.

For the most part, it’s the higher-level codes that matter for SEO. 400- and 500-level responses can prevent bots from crawling and indexing your pages. Too many of these errors can also indicate that your site isn’t of high quality, possibly lowering your rankings.

300-level codes have a bit more complicated relationship with SEO. The main thing you need to know to understand their impact is the difference between permanent and temporary redirects, which we’ll cover in more detail in the relevant section below.

In a nutshell, however, permanent redirects share link equity from backlinks, but temporary ones do not. In other words, when you use temporary redirects for pages that have moved, you lose the SEO advantage of all the link building you’ve done.

Checking for HTTP Status Codes in Google Search Console

One way to monitor how Google perceives the HTTP status codes on your site is to use Google Search Console. You can view 300-, 400-, and 500-level status codes in the Coverage report:

Google Search Console’s Coverage report

This area of your dashboard shows four types of content on your site:

You may find pages with 300-, 400-, and 500-level HTTP status codes under the Excluded, Error, or Valid with warnings sections, depending on the type of code. For instance, 301 redirects may be listed under Excluded as Page with redirect:

A page with a redirect in Google Search Console’s Coverage report.

400- and 500-level status codes will likely turn up under Error.

Another way to view HTTP status codes is by using the URL Inspection tool. If Google is unable to index a specific page due to an error, you’ll see that here:

A 404 error in Google Search Console’s URL Inspection tool

For more tips on using Google Search Console, check out our comprehensive guide to the platform.

A Complete Guide and List of HTTP Status Codes

While there are over 40 different server status codes, you’ll likely encounter fewer than a dozen on a regular basis. Below, we’ve covered the more common ones, as well as a few of the more obscure codes you may still run across.

Stumped by an HTTP status code? Our WordPress experts are standing by. Try Kinsta for Free.

100 Status Codes

A 100-level status code tells you that the request you’ve made to the server is still in progress for some reason. This isn’t necessarily a problem, it’s just extra information to let you know what’s going on.

200 Status Codes

This is the best kind of HTTP status code to receive. A 200-level response means that everything is working exactly as it should.

300 Status Codes

Redirection is the process used to communicate that a resource has been moved to a new location. There are several HTTP status codes that accompany redirections, in order to provide visitors with information about where to find the content they’re looking for.

400 Status Codes

At the 400 level, HTTP status codes start to become problematic. These are error codes specifying that there’s a fault with your browser and/or request.

Stumped by an HTTP status code? Our WordPress experts are standing by. Try Kinsta for Free.

500 Status Codes

500-level status codes are also considered errors. However, they denote that the problem is on the server’s end. This can make them more difficult to resolve.

Where to Learn More About HTTP Status Codes

In addition to the HTTP status codes we’ve covered in this list, there are some more obscure ones you may want to learn about. There are several resources you can consult to read up on these rarer codes, including:

Knowing these status codes may help you resolve some unique issues while maintaining your own website, or even when you encounter them on other sites.

Summary

While they may seem confusing or intimidating on the surface, HTTP status codes are actually very informative. By learning some of the common ones, you can troubleshoot problems on your site more quickly.

In this post, we’ve defined 40+ HTTP status codes that you may encounter. From the milder 100- and 200-level codes to the trickier 400- and 500-level errors, making sense of these messages is crucial for maintaining your website and making sure it’s accessible to users.

Save time, costs and maximize site performance with:

All of that and much more, in one plan with no long-term contracts, assisted migrations, and a 30-day-money-back-guarantee. Check out our plans or talk to sales to find the plan that’s right for you.

What HTTP status response code should I use if the request is missing a required parameter?

I am thinking 412 (Precondition Failed) but there may be a better standard?

9 Answers 9

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Status 422 seems most appropiate based on the spec.

The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.

They state that malformed xml is an example of bad syntax (calling for a 400). A malformed query string seems analogous to this, so 400 doesn’t seem appropriate for a well-formed query-string which is missing a param.

Note: Since the above RFC is about WebDAV there can be a misunderstanding that 422 and some others are only to be used in the context of WebDAV and using them outside of it is «nonstandard». But this only means these status codes were introduced in the context of this RFC. Indeed the wording of these definitions is carefully chosen not to be specific to WebDAV.

Why Does my HttpWebRequest Return 400 Bad request?

The following code fails with a 400 bad request exception. My network connection is good and I can go to the site but I cannot get this uri with HttpWebRequest.

4 Answers 4

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

First, cast the WebRequest to an HttpWebRequest like this:

Then, add this line of code:

Set UserAgent and Referer in your HttpWebRequest:

There could be many causes for this problem. Do you have any more details about the WebException?

One cause, which I’ve run into before, is that you have a bad user agent string. Some websites (google for instance) check that requests are coming from known user agents to prevent automated bots from hitting their pages.

In fact, you may want to check that the user agreement for YouTube does not preclude you from doing what you’re doing. If it does, then what you’re doing may be better accomplished by going through approved channels such as web services.

HTTP Status Codes For Invalid Data: 400 vs. 422

Let’s say that someone makes a request to your server with data that is in the correct format, but is simply not «good» data. So for example, imagine that someone posted a String value to an API endpoint that expected a String value; but, the value of the string contained data that was blacklisted (ex. preventing people from using «password» as their password). What HTTP status code would you return?

Until now, I would have returned a «400 Bad Request», which, according to the w3.org, means:

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

This description doesn’t quite fit the circumstance; but, if you go by the list of core HTTP status codes defined in the HTTP/1.1 protocol, it’s probably your best bet.

Recently, however, Jamie Krug pointed out [to me] that popular APIs are starting to use HTTP extensions to get more granular with their error reporting. Specifically, many APIs, like Twitter and Recurly, are using the status code «422 Unprocessable Entity» as defined in the HTTP extension for WebDAV. HTTP status code 422 states:

Going back to our password example from above, this 422 status code feels much more appropriate. The server understands what you’re trying to do; and it understands the data that you’re submitting; it simply won’t let that data be processed.

HTTP status code 422 feels like a much more appropriate response for situations where the data is understood, but is still not valid. I think I’ll start using this going forward. Thanks Jamie!

Enjoyed This Post? ❤️ Share the Love With Your Friends! ❤️

Reader Comments

Great catch. I’ll have to add that one to my list of things to watch out for in all of the remote services I’ve been working on lately.

My pleasure! When I first read a spec definition for 422, it still didn’t feel like a perfect fit, but it does seem better fit than 400. Cheers.

Yeah, still seems a bit odd. Like, what about if you go to create a NEW user, but provide a blacklisted email address? There is no «entity» yet to process. But, I guess it means you can’t create an entity to process. anyway, seems like an upgrade from 400.

. or maybe I am using the term «entity» in too narrow a view. Maybe they just mean «data entity», not «object entity.»

I agree, 400 shouldn’t be used here, as the http request is syntactically valid and conform to the protocol specifications.

If you write a custom client application or any other form of machine-machine interface, it may have a more distinct meaning (other than «something went wrong»), but nobody stops you from using 499 or any other custom 4xx code anyway.

By starting to rely on non-2xx responses for errors, it means that successful responses can simply return the «payload» and error handlers can take error messages. It’s been a long journey, but I have found that this is a bit more of an elegant and useful solution.

But, like I said, I was returning 200 for years and obviously, it worked, so I’m not saying it’s a bad move.

I stumbled across this a while back. Maybe from your site!

The (ColdFusion 9) code will dump a list of HTTP status codes.

Oh cool. It’s been a while since I’ve toyed around in the underlying page response object. Good stuff!

Nah, 400 is correct in this case. «Syntax» doesn’t just mean «well-formed XML» (or JSON or post data or whatever), it means that it’s syntactically correct in the context of the application.

This is not the case here.

As a POST body can contain arbitrary data, a problem with these data can only arise when the provided mime types does not match the body encoding (i.e. «application/x-www-form-urlencoded» when sending an XML or JSON body), or the encoding is invalid (bad XML structure, for instance).

These are all encoding (syntax) problems.

If there is no problem interpreting the body data, but a problem with the contents of these data (like Ben outline in the opening post), a 400 status code is not justified.

I don’t read the spec that way: if an XML request entity is not well-formed then respond 400 and say «couldn’t parse XML» in the response body, and if it has a «foo» element in place of a «bar» then respond 400 and say «found foo in place of bar» in the response. I understand the nuanced situation 422 is supposed to address, I just don’t think it’s necessary.

406 and 409 are completely wrong in this context.

If a problem arises from the payload (does not matter if syntactical or semantical), it is not a problem directly related to the http transport mechanism, and should not be indicated with http means.

This is a bit above my philosophical pay-grade, but perhaps the problem is that the HTTP spec was written before there was such a huge focus on 3rd-party APIs. As such, not very much was built into the spec to transport meta-data about the response?

Or maybe they [who designed HTTP] were just expecting all data to be returned inside a content body, like a SOAP envelope?

My biggest concern with wrapping error data inside a body transport is that the receiver-side of the API request needs to then be able to differentiate two different kinds of failures: HTTP failures (such as 400) and business-logic failures. And, if the latter is wrapped in a response with a 200OK status code, then the receiver needs to examine the OK responses more deeply to figure out if they were a success or a failure.

But again, I’m just a developer with zero experience in networking; so, I won’t be pretend to say any of the above with any confidence 🙂

but wasn’t that exactly my point to not mix up HTTP transport and business-logic?

Granted, it is convenient to report a problem in the http status code already (and save the hassle of parsing the http body), but.

That’s why there is no appropriate http status code for «something went wrong in the business logic layer», and frankly, if we start to add such http result codes, we will have a gazzillion new error codes in no time.

Just imagine this:
Your business logic only calls fetchData() with the URL and (optional body data), and returns an already parsed JSON object or an integer status code on error.

The fetchData() subroutine handles all the http stuff, i.e. redirections are resolved automatically and re-requested, and everything that cannot be handled results in an error report (and leaves it to the business logic to decide what to do, i.e. try a different server)

This way, the business logic doesn’t «ooze» into the networking stuff and vice versa.

Both can be tested independently (you can do as many fetchData() calls for testing as you like) and the business logic can be tested by making fetchData() return whatever you need to test.

And the best part is that you can re-use your thoroughly tested network logic in other projects, as it is completely independent from any business logic.

This is the way to create rock solid code, the only way imho.

«Weeks of coding can save you hours of planning.»

I’m sorry, forgot to answer your question in my last post, so here you go:

The hyper text transfer protocol (HTTP) was originally designed by Roy Fielding, Tim Berners-Lee and others at CERN. It is meanwhile maintained by the IETF, just as any other RFC.

I guess I would quibble with «http status codes. have no relation to what happens in the business-logic layer.»

E.g., imagine an application where a given resource can only be DELETEd by certain users (admins, the resource owner, or whatever) as identified in the Authorization header. The determination for who can DELETE what is completely in the realm of business logic, but if a different user makes the request then a 403 response seems completely appropriate according to the spec.

http only defines access in a yes/no way (basic, digest and nowadays oauth), so if you have access to a resource (read-only is enough), you can’t reply wih a 403 Forbidden.

If you add more granularity (read: yes, delete:no), it all happens in the business logic, and has to be reported as part of the business logic (in the http body data).

When it is not a http problem, why indicate a http problem?

Someone using your service/API will curse you for days when it is not clear why a resource that he was able to read just seconds ago is now «Forbidden» all of a sudden.

How is DELETE beyond the scope of HTTP? It’s in the spec!

sorry, didn’t realize that you were talking about the DELETE request method.

The DELETE command is in the http itself (header), not in the http payload (body), and when you issue a DELETE it will be clear what a 403 in return means.

That’s entirely different to what happens in the http payload and should stay separated.

Please have a look at how i.e. apache handles WebDAV access rights, it’s all done in the server configuration.

If you write your own server/client application, which nobody else will ever use, then, by all means, go for it and (ab)use whatever you like.
But if you write code like that for a public API, stick to what other people (read: fellow coders) know and expect (even if that’s not always 100% standard).
If i’d receive a 4xx error in return when calling your API, the last thing i’d consider is a problem within the body data.

Fair enough. By the same token, if I were to attempt to update a resource with a PUT request when calling *your* API, and got a 200 status in response, then the last thing I would expect is that the resource might not in fact have been updated.

Always interesting to hear other perspectives on stuff like this, though. Thanks!

Why would i respond to a PUT operation with a 200 when an error occurs?

That’s a plain vanilla http operation, hence the use of http status code is not only justified, it is mandatory.
(i.e. 201 Created or something like that)

There are, besides WebDAV, no applications using PUT or DELETE «in the wild», so this is a merely academical consideration. The specs list a lot of stuff that was meant to become part of HTTP/1.2 or even 2.0 (like 402 Payment Required).

Don’t do that, if you really hate parsing that much, how about adding a custom header field instead to indicate success/failure of the operation?
But you should return the error in the body nonetheless.

«Why would i respond to a PUT operation with a 200 when an error occurs?»

So what do you use then? A client tries to PUT a resource and you determine that for whatever reason it’s invalid in the context of your application and reject the request. The status code you use is.

Frankly, i wouldn’t use PUT at all, there are other means to upload a file (i.e. mimic the behaviour of a html FORM elements and send a multipart/form-data encoded body)

But, let’s say i would need it for a project (not trying to dodge your question here), i’d implement WebDAV (as far as i need it) and return a status code in compliance with the WebDAV specs.

This way i am using either RFC2616 (HTTP/1.1) or RFC2518 (WebDAV) and not some homegrown, incompatible modifications to standards.

If the error is a result of a http operation, report the error with an appropriate http status code.
If it’s WebDAV operation (DELETE, PUT. ) use the http status codes including those added for WebDAV.
If the error occurs in the business logic, report the error in the body and use 200 Ok

There are a few exceptions though, i.e. the business logic should be able to trigger a 500 response when something really goes foobar and replying with a proper response in the body is not possible.

Cool, I think we are just coming at things from totally different perspectives. If your API is limited to GETs and form data, then I can see that you wouldn’t be able to rely on status codes as much as is possible in a more RESTful design.

FWIW, PUT is very much part of HTTP/1.1 and in no way homegrown or limited to WebDAV (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6).

I know, i was the one coming up with the specs, but «commonly used like that» outweights the specs by far.

I have never seen any good use of PUT and DELETE outside of WebDAV, and not even WebDAV is much used.
(Microsofts fault mainly, but let’s better not go there)

«I have never seen any good use of PUT and DELETE outside of WebDAV, and not even WebDAV is much used. «

I mostly agree. For years, I used nothing but GET and POST and I was able to build very robust applications. I pretty much never use PUT. DELETE, I use.

own API, own client = do whatever you like.
A «488 Ben says: Invalid parameter type» would work fine, too, not sure why you make an effort to find an appropriate existing status code when you don’t stick to standards anyway. 😉
Every 4xx status code should work fine with any http(s) library out there.

However, i, for one, would still not do that (nor hire someone who does):
Imagine you win the lottery and move to Hawaii, and your customers are stuck with heavily customized code nobody can maintain/enhance.
Same goes for own projects, you might be too busy to code everything yourself one day and hire someone who runs into the same problem.

There is a sizable part of me which *wants* to follow standards; which I guess is why I’ve been trying hard to find an existing code that makes sense. But, I do all that in the context of not having a perfect grasp of the standard.

As far as efficiency goes, I’m not concerned about the data transfer. I agree that passing a small amount of JSON data would be negligibly different from passing an HTTP status code and text response. When I talk about «efficiency», I mean in the way the response is actually handled on the client-side.

Imagine that all the AJAX requests to the server are encapsulated behind a Promise object which allows for success/error bindings. If an error can cause both 4xx responses (HTTP error) and 2xx responses (application error), then there is an extra layer of checking in my client-side success handlers (pseudo code):

By shoe-horning application errors into «http errors,» then I can have a simpler separation between «success» and «fail» responses. That’s what I mean by efficiency.

you still shouldn’t «bend» the standards for that.

You have posted a tricky example, because request.done can’t call request.fail here directly, but if don’t use a lambda style function for fail here and instead pass a static function, you can.

It’s only a few more additional lines, plus, the static errorHandler function is way more efficient than creating a new lambda-style function every time you make an ajax request.
(Actually, deferred object are real resource hogs, as you create all the functions anew for every new promise object, but i digress. )

A few years ago, when Promises were first introduced to jQuery, I did play around with using the pipe() method and wrapper promises to actually shoe-horn structured responses into the a single error handler:

Without having to read those, the gist of the posts is that the server always returns a structured response with a 200 OK status. Then, on the client, the pseudo-code is as follows:

In those old posts, I actually DO return a 200 OK response for all «successful» HTTP requests, and then encapsulate the business-logic-failure within the structure response. Then, I use a response preprocessor to route the response to the error-handler IF the business logic indicates a failure.

I’ve never really thought of the Promise as being a resource hog. I mostly assume that as long as we don’t create circular references in the closures to DOM elements, then memory [leaks] is not too much of a concern.

If you already did it this way before, i wonder why you don’t stick to that concept and try to dabble with http response codes now.

It feels a bit like you’re trying to evolve, to refine the way you do things, and take a step back without realizing it.

But i mentioned that only because you were so worried about efficiency, it’s not like it’a a big deal when the functions passed are somewhat small.

Definitely, I am always trying to evolve in my programming skills. And that probably is a two steps forward, one step back kind of thing.

I’ve never used AngularJS, and very likely never will.

And what i don’t really believe is that AngularJS kinda leaves you with no other (practicable) cchoice than abusing http status codes.

It seems we’ve taken a wrong turn somewhere, my example addressed your example, but that does not mean it is limited to Promise objects.

However, you already made a decision for the current project, so i can only hope that you remember my objections here when you start a new project.

It’s not just AngularJS: Backbone, Spine, and presumably pretty much every other frontend framework that’s around these days is geared towards talking to REST interfaces using the full assortment of methods and status codes defined in the HTTP spec.

That’s one reason it took me a minute to understand where you were coming from: eschewing PUT/DELETE and error statuses is a fairly eccentric approach, though of course you can make anything work.

every xmlhttprequest is «geared towards» the full set of request verbs/status codes.

If your particular frontend library is using well-documented (read:standardized) methods for other means, it is basically only mimicking http (and WebDAV).

SIP mimics http, too, but nobody would say that SIP is using http standards.

«If your REST implementation resorts to a wild mixture of http and WebDAV it is nonetheless a «homegrown» protocol and does not follow standards. «

Totally agree, that’s my original reason for not liking 422 in this case.

Our only difference is between «return 400 and an error description in the body» vs. «return 200 and an error description in the body.»

Responding «200 OK» to a request that failed is clearly contrary to the plain language of the HTTP spec.

but 400 is defined as follows (taken from RFC2616):

400 Bad Request
The request could not be understood by the server due to malformed syntax.

This applies to «malformed syntax» of the header only, because the standard does not define anything related to the body data.

The request per se succeded (you’ve sent back data, mind you!), the body actually contains valid data, so i opted for a 200.

My interpretation of RFC2616 is this (and that’s how i’ve implemented it in the past):

400 is merely a reply to a junk request, a port number that has been mistakenly used for a different protocol or out-of-sync (meaning the server tries to i.e. interprete parts of the body data as request), and what’s more important, the server should close the tcp connection directly after sending the response (header!), so the client won’t i.e. send an out-of-sync request over that tcp connection again.

According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4 all 4xx responses should describe the error in the response body.

I know, but it doesn’t make sense to simply repeat ‘Bad Request’ in the http body.
All of the scenarios that i’ve listed above indicate that the client would not interprete the response correctly/at all anyway.

And it makes even less sense to do that when your body contains a JSON string, that is not really suited to be displayed to the end-user.

I.e. no browser displays the 401 Unauthorized to the user, they use a pop-up window for user credentials, so it’s not like this basic rule applies to every 4xx code in the same way.

But that’s only a side scenario.
You ignored my main point though, the «malformed syntax» part covers only the http header and not the body.

Right, you don’t repeat «Bad Request,» you spell out the reason it was rejected. E.g., «the specified ‘foo’ must be between 7 and 12.»

IMHO 5xx errors are the exclusive domain of the web server, and 4xx are fine to return from the application.

Interestingly, just noticed the spec calls out 404 as «commonly used» when no other error status applies: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5

But also note that the HTTPbis working group’s draft describes 400 a little more broadly than the HTTP/1.1 spec: http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-22#page-57

I don’t think we’re ever going to agree on this. But I maintain that returning what is explicitly defined as a «success» response to a request that was not fulfilled is, at the very least, surprising.

I see where you’re coming from, but yes, we’re very likely not going to agree on this. at least not anytime soon. 😛

I, for one, would be surprised to have a 400 response with body data in the expected format (instead of a placeholder, i.e. human readable text/html instead of the expected JSON data)

A 200 response clearly contains something i can parse without having to worry that the server sent some placeholder text.

The server won’t send a 200 on it’s own when addressing a script, and that’s one of my main reasons to prefer it over any other 4xx/5xx code!

Thanks for the suggestion, I’ve been wanting to come up with a standardized way to handle exceptions for a long time. I used the same thing you did, a flag at the top level of the response with a 200, but that felt really wrong. We’re going to use 422 (or if people really don’t like using a WebDav extension, we’ll fallback to 400). In that case, the body of the response is going to contain a list of errors with our application specific error code, maybe some exception specific data and a message to display to the user.

Most public APIs use 4xx to indicate a business logic error, YouTube, Amazon, Twitter etc, so whether or not this fits the rigid definition of the standard, I would much rather go with what these large and technically savvy companies use/

Anyway, by your definition of HTTP status codes, 403 does not make any sense. 403 clearly states that the request was completely valid but the server is refusing to respond to it, for instance due to business rules.

the http request IS completely valid, because http does neither define nor perform checks of the http payload (that’s solely a matter of the business logic).

And it’s the business logic that refuses to complete the requested action.

Whether others use this or not is not authoritative, but, if you insist on indicating a business logic problem in a http status code, (unnecessarily intertwining business and transport logic), why not use a 4xx status code that doesn’t have an accurately defined meaning yet?

2. The HTTP error codes are indeed targeted to be interpreted by Stacks (first) but 99% percent of the time they get propagated to the user simply dressed up differently so the separation of concerns you argue for is pretty much semantics.

What not ok is that you are prepared to introduce complexity in the form of custom entity formats, unnecessary confusion and incompatibility with standard logging/debugging tooling just to avoid a deviating a bit.

Furthermore, on a conceptual level, I see no problem in having HTTP return a generic Application Error code. HTTP does not live in vacuum and if you noticed most of its core operations are defined in terms of (application) business processes (posting to a bulletin board etc. )

Think proportional, the standards will eventually get tuned to align with what’s on the ground.

i really have a hard time to take feedback riddled with lols for serious.

Nonetheless i’ll try to reply:
Engineering trade off is just a different term for «diluting the standards» here.

Rape http as much as you like, add new request verbs, 8xx status codes, whatever you please (or need to get your stuff done) but don’t go telling everyone it is still http.

Let me, once again, rephrase it, because it still appears to be a problem:
Basically, you have two options.
a) stick to the standard
b) create your own protocol (based on http)

If you option a) is your choice, there is no need to discuss this any further, because http does not define a status code for «bad payload data».

Standards are important. Imagine 1,000,000 coders and everyone is adding at discretion. which means there IS NO STANDARD anymore.
And with the standard you lose compatibility and interoperability.

To sum it up:
Don’t mess with the standards.
If you need more than the standards lets you do, DERIVE.
Best practice is to stick to the payload with your custom needs entirely.

If you can’t see the value (in this particular context) and you truly believe that by using the WebDAV 422 Status Code Extension to HTTP/1.1 for distinguishing application level errors is «diluting the standards», «Rape http as much as you like» then please accept my apology for misinterpreting the discussion.

And why should anyone need a custom parser?? Are you being serious??

If everybody may change standards at will, there will be (insert arbitrarily big number) of different «flavours» of that standard in a wink and that means there is no standard anymore.
Applies to every standard there is.

Why do you have such a hard time to accept something that is so painfully obvious?

Please, ask yourself what the purpose of having standards in the first place might be. A surprising insight is right in the line for your there.