Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version
Go to top

NodeJS REST server trials to validate effective scripting

, 7 May 2012
Trial of popular REST implimentations for NodeJS including the measuring of MongoDB insertion rates.
rest-stress.zip
rest-stress
.git
COMMIT_EDITMSG
config
description
FETCH_HEAD
HEAD
hooks
applypatch-msg.sample
commit-msg.sample
post-commit.sample
post-receive.sample
post-update.sample
pre-applypatch.sample
pre-commit.sample
pre-rebase.sample
prepare-commit-msg.sample
update.sample
index
info
exclude
logs
HEAD
refs
heads
master
remotes
origin
HEAD
master
objects
01
0f1d7448768a22080ef394b21f138fc2193f07
05
26e7aae6d10a517dd4765d42fafb0af19976d7
06
7b5b3dd48bbf7c3836e3147f8b83092bf0b899
ef85cad33989b244fbd7d20801159c4c5daf42
0b
22d45bde518fec30f608e46741847e27c2a227
f89c06c1fa24c129abead9c07f9b2b2caf8b12
0e
021221d66219cee25fa7e5826001dd7ac6c22a
11
e74ae401cf8ac8a01b12a20db6513cc498dd08
13
1f099f068e5c39faecb0d3bab4ebe83492e6c5
16
af8a1b39b0e84e41aa3ba44a7150d2c83ca773
17
05fc02333c7a30bc50a6f64b85651f2c3cc6a5
a4d42e856295e53aa21168d283a0821c3ee38d
1a
ff806678b579f68fb299806668974fac3821c9
1c
acc486b33cd3b44f2a18c584c1cd4489afa80b
21
9f1684e8d19e3138718d727952ed4481c8c83e
24
8fc6007f35c263eed9cbba41c0fa39fbe87356
25
4db02248c396fd24e5cac1f9f1762a55a1aeda
e8ee73ee6d7b6a94d3aa594541ea7f309cb35e
28
4d6c1fa920f512ea767d15c718c8b5f511c99e
ae8188d0901343be58777bfb488e78c991d442
29
68355e74e030673667edb8a061f05176d4bb65
2e
aa6bb4f7b69eac7ddc646c113cabb869a0eb6d
30
6eb5de416c3b65f780cc44e1fe146dc38a32bd
aef02ee4954a63acd7105a791828ed69fd7854
33
40d681d41c95f2abc17cafa2741174cd746e00
724e6b9392ace7a781878e00d830ca47c718ea
37
ec244f21f9685c9d49df2427033ce9f85664d3
3f
e631d0aef1ab5c4c74c13fda28d9399f8048b6
41
d20974ae6b044a58b6384bf78ead83d17b1da1
43
f525e7c5d8cc1561d8f6923e5aeb72ed6c7e0f
45
74be6d37cab0537af0cc2c3592e77b2ad67695
46
e305795c9fae4bb15d1b37bd62ef8605b5fe9d
47
0acc47549e22f7a2540e959370250b3204499f
8a2044973989ebb4b590434302cfcd7f14b86a
4a
99ca196a3d1e104ae788fdcb00b5344bc82478
4b
6165ea045fd81a338f69f01aa821d76e8483cc
4d
ae1b7e000b913572a5e80e02011e2b4fd1cb0c
52
6bb84f112a31f41bea52957600fc86ae41559b
53
09a03cd49df9862ca001cc95b91b50d1b1c0fb
58
f539eb177da517f828a62a6e4e20491d56b22c
5a
5eae75a81da424297df32bb01a1e31ebef0356
62
6adaf1100b88a88ba7704a24fe644439bb8ef0
63
80a7d80fab7ec5f7be919bfd128d1d36aafe84
65
0055eee1b974bd7ae2846ddc9cc79a16d9eaea
66
a346ffda8b5d750e0aaee21dd227846d859015
69
54b38ff63a85621d96584640f6a0d5ab2e5f59
fb9da154eefe36202fe545903076a48d3e3330
6b
8184f8eff8a84b43e35fa349b3bac12afe3215
6f
1d850bb09b5a80cf95df70c0c67fa93904585f
78
998884e829b0d40d80f6db7d1f07d2cc36a7a4
7a
c2ba6a21ff564a8001f2d4bde8d38ad711999c
82
4d04474332701c3c9c186ec449574e2077cde6
84
9415ca6e401e966f661a16a38436a8c90d3e93
89
cd00f13809daaa5e05e4b4f4be32b770b96792
8a
ab628eeddfc8f31c23a97eee9b7c180856805a
8b
028b38ad4f24f33b39f94c258eaeb20d8746ad
6f5779328a56ea26174f9bfa3b2c797a3cb017
8e
13c9e734a5d6d2a841f5c4e13613e9b2368138
405c8ce83552a9de24b438259a69d66d645def
91
dac53ce6ec6fa288640a24239cb9bc04d01d8f
92
2003b8433bcad6ce9778a37628d738faa26389
93
69e167f200638b416b648655f15d4671ce7372
97
4728cdda2729522c3707b96f0ed20431704c45
9a
9534c9ca489495b0c828d3058e1d88fa9ac3f7
9b
1a74e04bad1488892d8e5151a58fe5f8e49847
9d
32e507a9813290efcaf393d19f39eaa295ff9d
9e
65f2896866641a84250b78bb034b7102978643
a0
58e566b1c25cd22b45e45e2cb7967462eb5616
a4
ea3f0c04ca2eee285398339d6a4f45516a6ad0
a5
b95bcbe48aa4219b6ba69045fa85b21e28b07f
aa
48737d8579aa75f29de07cb4e526822fa0824b
d83e36abcec290099f34b94f4af5ed25e68c8e
ac
56460aefd760b09e1e228fe70a67ad437f941d
798ac3c717073966656c675102aa103ca3c155
ad
9206e1de1b3185e3e7cc63d749f2023077ad5c
b2
48c95c6ff9a5d970256e7ff116cd618079b877
b3
014503c02df410ddbc359bc411cddc7a3c8b28
bf
d4cadf7c15d3ae194cd9728fb363e8b95a3bf6
c0
69471c734258f6f6a284faf3d8b21486dedcc1
c2
ee439b5e90c14d63f6e982097222debe7f7745
f87f3bca2050f6d36ef8ce88942aed7b6e23db
c7
0699792ffc4d7531b59306ab33453a24cb25b5
cd
032e0c6ec5b8e4333ae8a64cfc8eb57969d49c
d2
83614f5cb28bb6bbe54441419e67b66c74f7ca
d4
f91d8db4fe56ad1038c5faeb25a970b8434d26
d5
b1eea6885c9d8b5fece918ff7573218062d8cc
da
cd787248e03b22ad13340ff6898602ec270d76
dc
a33b829875c8a947742ae39b89d3255335f175
df
efdf3a685d4d3773384002488a6414ff1033da
e2
06d70d8595e2a50675ba11de48efcfa012497d
a6f487c8104409a4a8817c0e5cb5bd7837be82
d2f9780b0367f5cb1dc66d46ecea380f7b90c2
e5
ef752b760e7fb29553349b5dcec4c8da094bb1
e7
911bdf58513ace76db9f20a59d2876f8b64d51
eb
d747c7d39320ff069f9d4ff52ad59f9e13d3b1
ee
3b182e3325d8bd9ebf52ce90708ac902c637ea
ef
732009884af9b6b096e81811b0d46bb1524342
f2
473e9ed146bd5d6f06ae6761bbb17359bfdb63
f3
307d0edb28d23039c48cebcf2ba4862ba28407
fc637e36f3e86191eae658136895976a5bf6d8
f5
ea78e3a497b94f62410babadd2e3619ae523bd
fd
0ec436e2794aa773c59af655dcf69a4c961c51
b9aaab713a7ac121e3b1e1cf6af7b5a6c9a5c1
info
pack
ORIG_HEAD
packed-refs
refs
heads
master
remotes
origin
HEAD
master
tags
.idea
.name
rest-stress.iml
scopes
docs
images
mongoInsertTrend.png
restMongoComparedRate.png
restMongoOverhead.png
restMongoRate.png
restOverhead.png
restRate.png
restSingleMongoRate.png
lib
README.md
servers
module.exports = {
    '100' : {
        message     : 'Continue',
        description : 'The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code.'
    },
    '101' : {
        message     : 'Switching Protocols',
        description : 'The server understands and is willing to comply with the client\'s request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response\'s Upgrade header field immediately after the empty line which terminates the 101 response.\n\nThe protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.'
    },
    '200' : {
        message     : 'OK',
        description : 'The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:\n\nGET an entity corresponding to the requested resource is sent in the response;\n\nHEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;\n\nPOST an entity describing or containing the result of the action;\n\nTRACE an entity containing the request message as received by the end server.'
    },
    '201' : {
        message     : 'Created',
        description : 'The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.\n\nA 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19.'
    },
    '202' : {
        message     : 'Accepted',
        description : 'The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.\n\nThe 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent\'s connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request\'s current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.'
    },
    '203' : {
        message     : 'Non-Authoritative Information',
        description : 'The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).'
    },
    '204' : {
        message     : 'No Content',
        description : 'The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.\n\nIf the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent\'s active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent\'s active view.\n\nThe 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.'
    },
    '205' : {
        message     : 'Reset Content',
        description : 'The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.'
    },
    '206' : {
        message     : 'Partial Content',
        description : 'The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.\n\nThe response MUST include the following header fields:\n\n    - Either a Content-Range header field (section 14.16) indicating\n      the range included with this response, or a multipart/byteranges\n      Content-Type including Content-Range fields for each part. If a\n      Content-Length header field is present in the response, its\n      value MUST match the actual number of OCTETs transmitted in the\n      message-body.\n    - Date\n    - ETag and/or Content-Location, if the header would have been sent\n      in a 200 response to the same request\n    - Expires, Cache-Control, and/or Vary, if the field-value might\n      differ from that sent in any previous response for the same\n      variant\n\nIf the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.\n\nA cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see 13.5.4.\n\nA cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.'
    },
    '300' : {
        message     : 'Multiple Choices',
        description : 'The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.\n\nUnless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content- Type header field. Depending upon the format and the capabilities of\n\nthe user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.\n\nIf the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.'
    },
    '301' : {
        message     : 'Moved Permanently',
        description : 'The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.\n\nThe new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).\n\nIf the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.'
    },
    '302' : {
        message     : 'Found',
        description : 'The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.\n\nThe temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).\n\nIf the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.'
    },
    '303' : {
        message     : 'See Other',
        description : 'The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.\n\nThe different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).'
    },
    '304' : {
        message     : 'Not Modified',
        description : 'If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.\n\nThe response MUST include the following header fields:\n\n      - Date, unless its omission is required by section 14.18.1\nIf a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.\n\n      - ETag and/or Content-Location, if the header would have been sent\n        in a 200 response to the same request\n      - Expires, Cache-Control, and/or Vary, if the field-value might\n        differ from that sent in any previous response for the same\n        variant\n\nIf the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.\n\nIf a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.\n\nIf a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.'
    },
    '305' : {
        message     : 'Use Proxy',
        description : 'The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.\n\n10.3.7 306 (Unused)\n\nThe 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.'
    },
    '307' : {
        message     : 'Temporary Redirect',
        description : 'The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.\n\nThe temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.\n\nIf the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.'
    },
    '400' : {
        message     : 'Bad Request',
        description : 'The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.'
    },
    '401' : {
        message     : 'Unauthorized',
        description : 'The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].'
    },
    '402' : {
        message     : 'Payment Required',
        description : 'This code is reserved for future use.'
    },
    '403' : {
        message     : 'Forbidden',
        description : '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.'
    },
    '404' : {
        message     : 'Not Found',
        description : 'The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.'
    },
    '405' : {
        message     : 'Method Not Allowed',
        description : 'The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.'
    },
    '406' : {
        message     : 'Not Acceptable',
        description : 'The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.\n\nUnless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.\n\nIf the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.'
    },
    '407' : {
        message     : 'Proxy Authentication Required',
        description : 'This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].'
    },
    '408' : {
        message     : 'Request Timeout',
        description : '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.\n\n10.4.10 409 Conflict\n\nThe request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough\n\ninformation for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.\n\nConflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can\'t complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.\n\n10.4.11 410 Gone\n\nThe requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.\n\nThe 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server\'s site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.\n\n10.4.12 411 Length Required\n\nThe server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.\n\n10.4.13 412 Precondition Failed\n\nThe precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.\n\n10.4.14 413 Request Entity Too Large\n\nThe server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.\n\nIf the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.\n\n10.4.15 414 Request-URI Too Long\n\nThe server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.\n\n10.4.16 415 Unsupported Media Type\n\nThe server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.\n\n10.4.17 416 Requested Range Not Satisfiable\n\nA server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)\n\nWhen this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type.\n\n10.4.18 417 Expectation Failed\n\nThe expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.'
    },
    '500' : {
        message     : 'Internal Server Error',
        description : 'The server encountered an unexpected condition which prevented it from fulfilling the request.'
    },
    '501' : {
        message     : 'Not Implemented',
        description : 'The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.'
    },
    '502' : {
        message     : 'Bad Gateway',
        description : 'The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.'
    },
    '503' : {
        message     : 'Service Unavailable',
        description : 'The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.\n\n'
    },
    '504' : {
        message     : 'Gateway Timeout',
        description : 'The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.'
    },
    '505' : {
        message     : 'HTTP Version Not Supported',
        description : 'The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.'
    }
};

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Jason Rudland
Architect Relavance
Canada Canada
No Biography provided
Follow on   Google+

| Advertise | Privacy | Mobile
Web04 | 2.8.140926.1 | Last Updated 7 May 2012
Article Copyright 2012 by Jason Rudland
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid