ajax应该是什么响应 [英] what would an ajax errorthrown response be

查看:280
本文介绍了ajax应该是什么响应的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的jquery中,我添加了这些:
jqXHR,textStatus,errorThrown



任何人都可以告诉我什么文本会来自他们。普通英文文本来自错误;如果可能,



感谢任何人的回答。

解决方案

jQuery ajax处理程序失败的参数确实是

  .fail(function(jqXHR,textStatus,errorThrown){... 

文档状态



该函数接收三个参数:




  • jqXHR对象

  • 描述错误类型的字符串。

  • 可选的异常对象(如果发生)



第一个是包含XMLHttpRequest的本机XHR对象。



第二个是一个字符串,包含抛出的错误类型。

可能的值( null 除外)为timeouterrorabortparsererror



第三个参数在HTTP错误时填充或发生 errorThrown 接收HTTP状态的文本部分,例如未找到内部服务器错误



注意:不会为跨域脚本和跨域JSONP请求调用错误处理程序。



第三个参数可能包含的所有4xx代码的列表如下



400错误请求
由于明显的客户端错误(例如,格式错误的请求语法,太大的大小,无效的请求消息构框或欺骗性请求路由),服务器无法或不会处理请求。



401未经授权(RFC 7235)
类似于403 Forbidden,但专门用于在需要验证并失败或具有尚未提供响应必须包括一个包含适用于所请求资源的挑战的WWW-Authenticate头字段。请参阅基本访问认证和摘要访问认证。 401语义意味着未认证,即用户没有必要的凭据。



402需要付款
保留以备将来使用。最初的意图是,这段代码可能被用作某种形式的数字现金或微支付方案的一部分,但没有发生,而且这个代码通常不被使用。如果特定的开发人员已经超出了请求的每日上限,Google Developers API会使用此状态。



403禁止
请求是有效的请求,但服务器拒绝回应。用户可能已经登录,但没有资源所需的权限。



404未找到
请求的资源可能未找到但可能在将来可用。客户端的后续请求是允许的。



405不允许的方法
所请求的资源不支持请求方法;例如,需要通过POST呈现数据的表单上的GET请求,或只读资源上的PUT请求。



406不可接受
请求的资源只能根据请求中发送的Accept标头生成不可接受的内容。



407代理验证必需(RFC 7235)
客户端必须首先使用代理身份验证。



408请求超时
服务器超时等待请求。根据HTTP规范:客户端在服务器准备等待的时间内没有产生请求,客户端可以随时重复请求而不进行修改。



409冲突
表示请求无法处理,因为请求中存在冲突,例如多个同步更新之间的编辑冲突。



410 Gone
表示请求的资源不再可用,不再可用。当资源被有意地删除并且资源应被清除时,应该使用这个。在收到410状态码后,客户端将来不应该请求资源。诸如搜索引擎的客户端应该从其索引中删除资源。大多数用例不需要客户端和搜索引擎来清除资源,可能会使用404 Not Found。



411需要长度
请求没有指定其内容的长度,这是所请求的资源所需的。



412前提条件失败(RFC 7232)
服务器不符合请求者对请求提出的前提条件。



413有效负载太大(RFC 7231 )
请求大于服务器愿意或能够处理的请求。以前称为请求实体太大。



414 URI太长(RFC 7231)
提供的URI太长服务器进行处理。通常将太多数据的结果编码为GET请求的查询字符串,在这种情况下,应将其转换为POST请求。



415不支持的媒体类型
请求实体具有媒体类型,服务器或资源不支持。例如,客户端将图像上传为image / svg + xml,但服务器要求图像使用不同的格式。



416范围不满意(RFC 7233)
客户端已经要求文件的一部分(字节服务),但服务器无法提供该部分。例如,如果客户端要求文件的一部分超出文件结尾。以前称为请求的范围不满足。



417期望失败
服务器无法满足Expect请求标头的要求字段。[49]
418我是一个茶壶(RFC 2324)
这个代码在1998年被定义为传统的IETF April Fools的笑话之一,在RFC 2324,超文本咖啡壶控制协议中,并不期望由实际的HTTP服务器实现。 RFC指定此代码应由要求冲泡咖啡的茶壶返回。

此HTTP状态在某些网站(包括Google.com)中用作复活节彩蛋。



421错误的请求(RFC 7540)
该请求针对的是无法产生响应的服务器(例如因为连接重用)。


422无法处理的实体(WebDAV; RFC 4918)
请求格式正确,但由于语义错误而无法遵循。 / p>

423锁定(WebDAV; RFC 4918)
正在访问的资源被锁定。



424失败的依赖关系(WebDAV; RFC 4918)
由于先前的请求失败(例如,PROPPATCH),请求失败。



426需要升级
客户端应该切换到不同的协议,如TLS / 1.0,在升级头字段中给出。



428前提条件(RFC 6585)
原始服务器要求请求是有条件的。旨在防止丢失更新问题,客户端获取资源的状态,修改它,并将其重新连接到服务器,同时第三方已修改服务器上的状态,导致冲突。



429太多请求(RFC 6585)
用户在给定的时间内发送了太多的请求。旨在用于限速方案。



431请求标头字段太大(RFC 6585)
服务器不愿意处理请求,因为单独的标题字段或所有标题字段集合都太大。



451不适用于法律原因
服务器运营商已经收到法定要求,以拒绝对资源或包含所请求资源的一组资源的访问。

选择代码451作为小说华氏451的参考。 / p>

这是普通英文的含义。


In my jquery I had added these: jqXHR, textStatus, errorThrown

Could anyone tell me what text would come from them. Plain English text from the error; if possible.

Thanks for anyone whom answers.

解决方案

The arguments for jQuery ajax handlers failing are indeed

.fail(function(jqXHR, textStatus, errorThrown) {...

The documentation states

The function receives three arguments:

  • The jqXHR object.
  • A string describing the type of error.
  • An optional exception object, if one occurred.

The first one is the native XHR object, containing the XMLHttpRequest.

The second one is a string containing the type of error thrown.
Possible values (besides null) are "timeout", "error", "abort", and "parsererror".

The third argument is populated when a HTTP error occurs, errorThrown receives the textual portion of the HTTP status, such as "Not Found" or "Internal Server Error".

Note: The error handler is not called for cross-domain script and cross-domain JSONP requests.

A list of all 4xx codes that the third argument could possibly contain is as follows

400 Bad Request The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).

401 Unauthorized (RFC 7235) 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. 401 semantically means "unauthenticated", i.e. the user does not have the necessary credentials.

402 Payment Required Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.

403 Forbidden The request was a valid request, but the server is refusing to respond to it. The user might be logged in but does not have the necessary permissions for the resource.

404 Not Found The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

405 Method Not Allowed A request method is not supported for the requested resource; for example, a GET request on a form which requires data to be presented via POST, or a PUT request on a read-only resource.

406 Not Acceptable The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

407 Proxy Authentication Required (RFC 7235) The client must first authenticate itself with the proxy.

408 Request Timeout The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."

409 Conflict Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.

410 Gone Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.

411 Length Required The request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed (RFC 7232) The server does not meet one of the preconditions that the requester put on the request.

413 Payload Too Large (RFC 7231) The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".

414 URI Too Long (RFC 7231) The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.

415 Unsupported Media Type The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.

416 Range Not Satisfiable (RFC 7233) The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously.

417 Expectation Failed The server cannot meet the requirements of the Expect request-header field.[49] 418 I'm a teapot (RFC 2324) This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.
This HTTP status is used as an easter egg in some websites, including Google.com.

421 Misdirected Request (RFC 7540) The request was directed at a server that is not able to produce a response (for example because a connection reuse).

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

423 Locked (WebDAV; RFC 4918) The resource that is being accessed is locked.

424 Failed Dependency (WebDAV; RFC 4918) The request failed due to failure of a previous request (e.g., a PROPPATCH).

426 Upgrade Required The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

428 Precondition Required (RFC 6585) The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict."

429 Too Many Requests (RFC 6585) The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.

431 Request Header Fields Too Large (RFC 6585) The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

451 Unavailable For Legal Reasons A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.
The code 451 was chosen as a reference to the novel Fahrenheit 451.

This is in "plain english" what the arguments would contain.

这篇关于ajax应该是什么响应的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆