Bill de blasio mayor lisette camilo commissioner the city of new york department of citywide administrative services application unit 1 centre street, 14 th floor. Technical Documentation. The Technical Documentation resources below are primarily available in PDF format. The Tutorials are ZIP files that contain a PDF tutorial. Get a new tip, trick, or troubleshooting technique for Revit every Tuesday. This weekly series offers workflow enhancements, customizations, and shortcuts for both.
List of HTTP status codes. This is a list of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETFinternet standards, other IETF RFCs, other specifications, and some additional commonly used codes.
The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human- readable alternative can be provided.
Unless otherwise stated, the status code is part of the HTTP/1. RFC 7. 23. 1). Since HTTP/1. Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 1. Continue status code in response before sending the body. The response 4. 17 Expectation Failed indicates the request should not be continued.
This code indicates that the server has received and is processing the request, but no response is available yet. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource.
This is a list of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and. University of Nevada Las Vegas (UNLV) College of Civil Engineering CEG 468/668 GIS Applications in Civil Engineering Spring 2004 Semester http://www.ce.unlv.edu.
In a POST request, the response will contain an entity describing or containing the result of the action. The request might or might not be eventually acted upon, and may be disallowed when processing occurs. Unlike a 2. 04 response, this response requires that the requester reset the document view. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. Many of these status codes are used in URL redirection. A user agent may automatically redirect a request.
A user agent should detect and intervene to prevent cyclical redirects. For example, this code could be used to present multiple video format options, to list files with different extensions, or to suggest word sense disambiguation.
The HTTP/1. 0 specification (RFC 1. Therefore, HTTP/1. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a redirect with a separate GET message. In such case, there is no need to retransmit the resource since the client still has a previously- downloaded copy. Many HTTP clients (such as Mozilla.
In contrast to how 3. For example, a POST request should be repeated using another POST request. HTTP method to change.
So, for example, submitting a form to a permanently redirected resource may continue smoothly. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. 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. 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.
The user might be logged in but does not have the necessary permissions for the resource. Not Found. The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
According to HTTP specifications: . The client MAY repeat the request without modifications at any later time. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 4. Clients such as search engines should remove the resource from their indices.
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. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. Range Not Satisfiable (RFC 7. 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. The RFC specifies this code should be returned by tea pots requested to brew coffee. Intended for use with rate- limiting schemes.
Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method. Usually this implies future availability (e.
API). Generally, this is a temporary state. Intended for use by intercepting proxies used to control access to the network (e. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage. A code of 4. 98 indicates an expired or otherwise invalid token.
A code of 4. 99 indicates that a token is required but was not submitted. Retrieved 1. 6 October 2. Retrieved January 8, 2.
Retrieved April 1, 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2.
HTTP Extensions for Distributed Authoring . Retrieved October 2. Hypertext Transfer Protocol - - HTTP/1. Retrieved August 3. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2.
Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. HTTP Extensions for Web Distributed Authoring and Versioning (Web. DAV). Retrieved October 2. Retrieved 1. 6 October 2.
Retrieved February 2. Retrieved 1. 3 February 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Hypertext Transfer Protocol . Retrieved October 2.
Retrieved June 1. It states: The redirection happens as a . Retrieved June 3. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2.
Retrieved May 2. 1, 2. Retrieved September 2. Internet Engineering Task Force. Retrieved 1. 6 October 2.
Retrieved January 8, 2. Retrieved 1. 6 October 2. Retrieved February 8, 2.
Retrieved September 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved February 4, 2. Retrieved 1. 6 October 2.
Retrieved 1. 6 October 2. Retrieved November 1. Retrieved 1. 6 October 2. Retrieved November 1. Retrieved 1. 6 October 2.
Retrieved November 1. Retrieved 1. 6 October 2. Hyper Text Coffee Pot Control Protocol (HTCPCP/1. Retrieved April 2. Network Working Group. Retrieved 1. 6 October 2. Internet Engineering Task Force.
Retrieved May 1, 2. Retrieved 7 March 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2. Retrieved 1. 6 October 2.
Retrieved 1. 6 October 2. Retrieved 1. 6 October 2.
Transparent Content Negotiation in HTTP. Retrieved October 2. An HTTP Extension Framework. Retrieved October 2. Retrieved 1. 6 October 2. Retrieved October 1. Arc. GIS Server SOAP SDK.
Retrieved October 1. Retrieved November 1.
Retrieved October 2. Retrieved January 8, 2.
Retrieved January 8, 2.