forked from teapot-php/status-code
-
Notifications
You must be signed in to change notification settings - Fork 0
/
StatusCode.php
816 lines (758 loc) · 35.1 KB
/
StatusCode.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
<?php
/**
* Interface representing standard HTTP status codes. These codes are
* represented as an interface so that developers may implement it and then use
* parent::[CODE] to gain a code, or to extend the codes using static::[CODE]
* and override their default description.
*
* This allows for codes to be repurposed in a natural way where the core,
* traditional use would not be meaningful.
*
* PHP version 5.3
*
* @category StatusCode
* @package Teapot
* @subpackage HttpResponse
* @author Barney Hanlon <barney@shrikeh.net>
* @copyright 2013 B Hanlon. All rights reserved.
* @license MIT http://opensource.org/licenses/MIT
* @link http://shrikeh.github.com/teapot
*/
namespace Teapot\HttpResponse\Status;
/**
* Interface representing standard HTTP status codes. These codes are
* represented as an interface so that developers may implement it and then use
* parent::[CODE] to gain a code, or to extend the codes using static::[CODE]
* and override their default description.
*
* This allows for codes to be repurposed in a natural way where the core,
* traditional use would not be meaningful.
*
* @category StatusCode
* @package Teapot
* @subpackage HttpResponse
* @author Barney Hanlon <barney@shrikeh.net>
* @copyright 2013 B Hanlon. All rights reserved.
* @license MIT http://opensource.org/licenses/MIT
* @link http://shrikeh.github.com/teapot
*/
interface StatusCode
{
/**
* The request has succeeded. The information returned with the response is
* dependent on the method used in therequest, for example:
* GET an entity corresponding to the requested resource is sent in the
* response;
* HEAD the entity-header fields corresponding to the requested resource
* are sent in the response without any message-body;
* POST an entity describing or containing the result of the action;
* TRACE an entity containing the request message as received by the end
* server.
*
* @var integer
*/
const OK = 200;
/**
* 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.
*
* @var integer
*/
const CREATED = 201;
/**
* 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.
*
* The 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.
*
* @var integer
*/
const ACCEPTED = 202;
/**
* 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).
*
* @var integer
*/
const NON_AUTHORATIVE_INFORMATION = 203;
/**
* 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.
* If 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.
*
* The 204 response MUST NOT include a message-body, and thus is always
* terminated by the first empty line after the header fields.
*
* @var integer
*/
const NO_CONTENT = 204;
/**
* 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.
*
* @var integer
*/
const RESET_CONTENT = 205;
/**
* The server has fulfilled the partial GET request for the resource. The
* request MUST have included a Range header field indicating the desired
* range, and MAY have included an If-Range header field (section 14.27) to
* make the request conditional.
* The response MUST include the following header fields:
*
* - Either a Content-Range header field (section 14.16) indicating
* the range included with this response, or a multipart/byteranges
* Content-Type including Content-Range fields for each part. If a
* Content-Length header field is present in the response, its
* value MUST match the actual number of OCTETs transmitted in the
* message-body.
* - Date
* - ETag and/or Content-Location, if the header would have been sent in a
* 200 response to the same request
* - Expires, Cache-Control, and/or Vary, if the field-value might differ
* from that sent in any previous response for the same variant
*
* If 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.
* A 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.
*
* A cache that does not support the Range and Content-Range headers
* MUST NOT cache 206 (Partial) responses.
*
* @var integer
*/
const PARTIAL_CONTENT = 206;
/**
* The requested resource corresponds to any one of a set of
* representations, each with its own specific location, and agent-driven
* negotiation information is being provided so that the user (or user
* agent) can select a preferred representation and redirect its request
* to that location.
* Unless 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 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. If 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.
*
* @var integer
*/
const MULTIPLE_CHOICES = 300;
/**
* 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.
* The 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).
* If 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.
*
* Note: When automatically redirecting a POST request after
* receiving a 301 status code, some existing HTTP/1.0 user agents
* will erroneously change it into a GET request.
*
* @var integer
*/
const MOVED_PERMANENTLY = 301;
/**
* 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.
* The 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).
* If 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.
*
* Note: RFC 1945 and RFC 2068 specify that the client is not allowed
* to change the method on the redirected request. However, most
* existing user agent implementations treat 302 as if it were a 303
* response, performing a GET on the Location field-value regardless
* of the original request method. The status codes 303 and 307 have
* been added for servers that wish to make unambiguously clear which
* kind of reaction is expected of the client.
*
* @var integer
*/
const FOUND = 302;
/**
* 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.
* The 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).
* Note: Many pre-HTTP/1.1 user agents do not understand the 303
* status. When interoperability with such clients is a concern, the
* 302 status code may be used instead, since most user agents react
* to a 302 response as described here for 303.
*
* @var integer
*/
const SEE_OTHER = 303;
/**
* 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.
* The response MUST include the following header fields:
* - Date, unless its omission is required by section 14.18.1
* If 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.
* - ETag and/or Content-Location, if the header would have been sent
* in a 200 response to the same request
* - Expires, Cache-Control, and/or Vary, if the field-value might
* differ from that sent in any previous response for the same variant
*
* If 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.
* If a 304 response indicates an entity not currently cached, then the
* cache MUST disregard the response and repeat the request without the
* conditional.
* If 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.
*
* @var integer
*/
const NOT_MODIFIED = 304;
/**
* 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.
* Note: RFC 2068 was not clear that 305 was intended to redirect a
* single request, and to be generated by origin servers only.
* Not observing these limitations has significant security
* consequences.
*
* @var integer
*/
const USE_PROXY = 305;
/**
* 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.
* The 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.
* If 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.
*
* @var integer
*/
const TEMPORARY_REDIRECT = 307;
/**
* The request could not be understood by the server due to malformed
* syntax. The client SHOULD NOT repeat the request without modifications.
*
* @var integer
*/
const BAD_REQUEST = 400;
/**
* 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].
*
* @var integer
*/
const UNAUTHORIZED = 401;
/**
* This code is reserved for future use.
*
* @var integer
*/
const PAYMENT_REQUIRED = 402;
/**
* 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.
*
* @var integer
*/
const FORBIDDEN = 403;
/**
* 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.
*
* @var integer
*/
const NOT_FOUND = 404;
/**
* 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.
*
* @var integer
*/
const METHOD_NOT_ALLOWED = 405;
/**
* 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.
*
* Unless 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.
* Note: HTTP/1.1 servers are allowed to return responses which are
* not acceptable according to the accept headers sent in the request.
* In some cases, this may even be preferable to sending a 406
* response. User agents are encouraged to inspect the headers of an
* incoming response to determine if it is acceptable.
*
* If 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.
*
* @var integer
*/
const NOT_ACCEPTABLE = 406;
/**
* 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].
*
* @var integer
*/
const PROXY_AUTHENTICATION_REQUIRED = 407;
/**
* 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.
*
* @var integer
*/
const REQUEST_TIMEOUT = 408;
/**
* The 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
* information 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.
* Conflicts 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.
*
* @var integer
*/
const CONFLICT = 409;
/**
* The 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.
*
* The 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.
*
* @var integer
*/
const GONE = 410;
/**
* The 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.
*
* @var integer
*/
const LENGTH_REQUIRED = 411;
/**
* The 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.
*
* @var integer
*/
const PRECONDITION_FAILED = 412;
/**
* The 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.
* If 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.
*
* @var integer
*/
const REQUEST_ENTITY_TOO_LARGE = 413;
/**
* The 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.
*
* @var integer
*/
const REQUEST_URI_TOO_LONG = 414;
/**
* The 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.
*
* @var integer
*/
const UNSUPPORTED_MEDIA_TYPE = 415;
/**
* A 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.)
* When 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.
*
* @var integer
*/
const REQUESTED_RANGE_NOT_SATISFIABLE = 416;
/**
* The 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.
*
* @var integer
*/
const EXPECTATION_FAILED = 417;
/**
* The HTCPCP server is a teapot; the resulting entity may be short and
* stout. Demonstrations of this behaviour exist.
*
* @var integer
*/
const I_AM_A_TEAPOT = 418;
/**
* The policy for accessing the resource has not been met in the request.
* The response MUST include a PEP-Info or a C-PEP-Info header field
* specifying the extensions required by the publishing party for accessing
* the resource. The server MAY use the for attribute bag to indicate
* whether the policy applies to other resources.
*
* The client MAY repeat the request using the appropriate extensions). If
* the initial request already included the extensions requested in the 420
* response, then the response indicates that access has been refused for
* those extension declarations.
* If the 420 response contains the same set of extension policies as the
* prior response, then the client MAY present any entity included in the
* response to the user, since that entity may include relevant diagnostic
* information.
* Implementers may note the similarity to the way authentication
* challenges are issued with the 401 (Unauthorized) status-code.
*
* @var integer
*/
const POLICY_NOT_FULFILLED = 420;
/**
* The mappings indicated by one or more map attribute bags in the request
* were not unique and mapped the same header field more than once.
* The client MAY repeat the request using a new set of mappings if it
* believes that it can find a unique set of header fields for which the
* transaction will succeed.
*
* @var integer
*/
const BAD_MAPPING = 421;
/**
* 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.
*
* @var integer
*/
const UNPROCESSABLE_ENTITY = 422;
/**
* The 423 (Locked) status code means the source or destination resource
* of a method is locked. This response SHOULD contain an appropriate
* precondition or post-condition code, such as 'lock-token-submitted' or
* 'no-conflicting-lock'.
*
* @var integer
*/
const ENTITY_LOCKED = 423;
/**
* The 424 (Failed Dependency) status code means that the method could not
* be performed on the resource because the requested action
* depended on another action and that action failed. For example, if a
* command in a PROPPATCH method fails then, at minimum, the rest
* of the commands will also fail with 424 (Failed Dependency).
*
* @var integer
*/
const FAILED_DEPENDENCY = 424;
/**
* The Upgrade response header field advertises possible protocol upgrades
* a server MAY accept. In conjunction with the "426 Upgrade Required"
* status code, a server can advertise the exact protocol upgrades that a
* client MUST accept to complete the request. The server MAY include an
* Upgrade header in any response other than 101 or 426 to indicate a
* willingness to switch to any (combination) of the protocols listed.
*
* @var integer
*/
const UPDATE_REQUIRED = 426;
/**
* The origin server requires the request to be conditional. Its typical
* use is to avoid 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. By requiring requests to be conditional, the server can
* assure that clients are working with the correct copies.
*
* @var integer
*/
const PRECONDITION_REQUIRED = 428;
/**
* The user has sent too many requests in a given amount of time.
*
* @var integer
*/
const TOO_MANY_REQUESTS = 429;
/**
* The server is unwilling to process the request because its header fields
* are too large.
*
* @var integer
*/
const REQUEST_HEADER_FIELDS_TOO_LARGE = 431;
/**
* The server encountered an unexpected condition which prevented it from
* fulfilling the request.
*
* @var integer
*/
const INTERNAL_SERVER_ERROR = 500;
/**
* 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.
*
* @var integer
*/
const NOT_IMPLEMENTED = 501;
/**
* 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.
*
* @var integer
*/
const BAD_GATEWAY = 502;
/**
* 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.
* Note: The existence of the 503 status code does not imply that a
* server must use it when becoming overloaded. Some servers may wish to
* simply refuse the connection.
*
* @var integer
*/
const SERVICE_UNAVAILABLE = 503;
/**
* 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.
* Note: Note to implementors: some deployed proxies are known to
* return 400 or 500 when DNS lookups time out.
*
* @var integer
*/
const GATEWAY_TIMEOUT = 504;
/**
* 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.
*
* @var integer
*/
const HTTP_VERSION_NOT_SUPPORTED = 505;
/**
* Transparent content negotiation for the request results in a circular
* reference.
*
* @var integer
*/
const VARIANT_ALSO_NEGOTIATES = 506;
/**
* The server is unable to store the representation needed to complete the
* request.
*
* @var integer
*/
const INSUFFICIENT_STORAGE = 507;
/**
* The server detected an infinite loop while processing the request
* (sent in lieu of 208).
*
* @var integer
*/
const LOOP_DETECTED = 508;
/**
* This status code, while used by many servers, is not specified in any
* RFCs.
*
* @var integer
*/
const BANDWIDTH_LIMIT_EXCEEDED = 509;
/**
* Further extensions to the request are required for the server to fulfill
* it.
*
* @var integer
*/
const NOT_EXTENDED = 510;
/**
* The client needs to authenticate to gain network access.
*
* @var integer
*/
const NETWORK_AUTHENTICATION_REQUIRED = 511;
}