817:
736:
31:
1105:
925:
672:
557:
213:
1161:
1005:
614:
262:
336:
So no, there's no decimal code. The status code is used by the client to take an action, e.g. prompt for a password, re-fetch from a different location, etc. If a server output a dodgy code it would confuse the client, though it's worth remembering that what you see in the client is usually a HTML
327:
The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user.
841:
template. Perhaps it really would be better-placed in 418, but even still, consensus should be reached. I would point out that error 418 is notable by WP standards, but since it seems only
Mozilla extends the joke to include 503. Are there any news articles talking about this joke extension? --
760:
template. As humorous as this is, I think adding the joke information from "418" to the entirely serious description of "503" is probably undue. I could see adding it as a qualification to the description of "418" itself, but it's certainly not an uncontroversial change to be added via an edit
92:
Looking at 509, it cites "(Apache Web Server/cPanel)", but only has a reference for cPanel. Following that link, it says "Your server reached the bandwidth limit that the system administrator imposed. The only solution for this issue is to wait until the limit resets in the following cycle. To
356:
IIS has different ways of handling the same error depending on how it was caused. It returns the correct status code to the user, however, its default error pages also have sub-codes for explaining the particular circumstances behind an error. While there are numerous 401.x or 403.x pages,
776:
Yeah, it probably would be better if instead of modifying the 503 error section, this was added to the 418 section: It should also be noted that if a coffeepot/teapot is out of coffee, it should return a 503 error, according to the
Mozilla Developer Docs (link/ref here)
1139:
Reasoning: The same sentence explains it. means that the user does not have a valid authentication. This means unauthenticated. Unauthorized would be 403. HTTP code naming is just confusing here. See the following
Mozilla link, where it uses the same definition
99:
I also had a look through many Apache bandwidth limitation modules, but couldn't find any that actually generate 509, or recommend doing so. As such, I suspect that one of these modules might have done so long ago, but doesn't any more.
532:. I think "is not expected to be" is still better here since the sites using 418 obviously don't actually implement HTCPCP ("is rarely", in my opinion, implies that the sites use this status code appropriately).
703:
Change the 503 error code category to also include the fact that
Mozilla Developer Docs say that this is the error code that should be returned when a coffee/teapot (see code 418) is out of coffee temporarily
269:; there is a small hidden comment in the source code explaining why, although I understand why you didn't notice it. This article is British English, so in particular "fulfil" is a valid spelling. See also
300:
5xx.x - too many clients connected to server try again later
Microsoft internet services ver x ( or whatever ms calls their webserver
883:
452:
370:
There is no referece for the existance of this status code and a quick look around turned up nothing. I've deleted it for now, unless anyone can find anything? Was initially added by
1136:
Last sentence of section
Unauthorized" states the following: 'semantically means "unauthorised"'. However it should be the following: ' semantically means "unauthenticated"'
337:
page generated by the server and is part of the body of the response ā which doesn't necessarily contain the same status information as it gives to the client in the header.
1041:
Could we fix a misspelling and change "fulfil" to "fulfill" on this line: 5xx server error ā the server failed to fulfil an apparently valid request Thank you, Cooper
167:
478:
Removed redundant refs to rfc that are not needed, because the intro says: "Unless otherwise stated, the status code is part of the HTTP standard (RFC 9110)."
72:
67:
59:
491:
With this cleanup, I also removed the 'User-generated' template that warned about "may contain improper references to user-generated content" --
529:
648:
Please be advised that LiteSpeed
Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.
720:
1060:
I suggest to add the following unofficial status code that puzzled some developers. The code was generated by LinkedIn. For more info, see:
1183:
1064:
902:
887:
528:
Some sites apparently use 418 instead of 403 when blocking a request for some reason. I've added some text mentioning this here and in
649:
456:
427:
245:
1061:
518:
510:
Would it be appropriate to change the 418 discussion from "is not expected to be" to "is rarely"? I just got a 418 response from
1024:
636:
168:
https://softwareengineering.stackexchange.com/questions/21339/which-http-response-do-you-return-to-a-hit-from-a-blacklisted-ip
47:
17:
96:
That sounds like cPanel is giving advice about the server generating the 509, not saying that cPanel generates it itself.
836:
755:
514:
125:
1148:
38:
1141:
1115:
935:
682:
567:
278:
223:
193:
1144:
724:
522:
1187:
1068:
906:
1111:
931:
829:
748:
678:
563:
431:
219:
185:
166:
Hi, can't edit the page - how's this for a cite regarding the reasons for wrong use in 401 for banned ips?
653:
601:
249:
152:
138:
130:
Maybe just a link to a page of samples? Anyone know of one? If I find them, would it be good to add them?
371:
1046:
991:
1172:
1086:
867:
859:
847:
843:
782:
709:
448:
423:
I have not done a full audit but one example is HTTP Code 422, now known as "Unprocessable
Content".
274:
189:
148:
134:
1191:
1176:
1152:
1089:
1072:
1050:
1030:
1019:
995:
910:
891:
871:
851:
824:
786:
770:
743:
728:
713:
657:
642:
632:
605:
541:
537:
500:
460:
435:
403:
380:
282:
253:
197:
178:
156:
142:
114:
1062:
https://learn.microsoft.com/en-us/archive/msdn-technet-forums/5a4f8eb5-bf1b-4776-b4bb-4baef621838f
170:
1042:
987:
766:
376:
341:
417:
804:
496:
424:
399:
174:
980:
Unofficial 407 - on start of the line is ":" instead of ";", aware 407 is in this list twice!
391:
270:
1168:
1079:
863:
778:
705:
597:
294:
304:
this was a while ago so i'm not sure if i remeber this right, but i was just wondering.
1014:
625:
533:
110:
762:
103:
Does anyone have an actual reference for software that generates 509 in this manner?
862:
Not that I'm aware of no, I've edited the 418 official page to include this though.
481:
Removed refs that repeated content from rfcs, but with no significant clarifications
492:
395:
358:
349:
305:
46:
If you wish to start a new discussion or revive an old one, please do so on the
1142:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#client_error_responses
413:
416:
has been published as of June 2022. It provides updates to HTTP status codes
106:
293:
Is there an http error code with a decimal code? I thought i once saw a
390:
rfc-9110 just released, obsoleting parts of previous rfcs 723x series,
593:
897:
Hello po paki tulong Naman nag withrow ako Hindi dumating sa gcash ko
475:
Updated old rfcs refs to use new rfc 911x series (released June 2022)
511:
484:
Removed refs specific to a particular context (app, framework, etc)
328:
The client is not required to examine or display the Reason-Phrase.
357:
officially they are all classed as their respective main class.
321:
Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
1099:
919:
666:
551:
207:
25:
986:
Unofficial 611 - on start of the line is ":" instead of ";"
805:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
348:
okay. I was just wondering because I thought I saw on once.
983:
Unofficial 770 - on start of the line is ":" instead of ";"
394:. References on this page eventually need to be updated.
392:
https://datatracker.ietf.org/doc/html/rfc9110#section-1.4
93:
resolve this issue, contact your system administrator."
588:
Change the article link for "Unofficial Code 218" from
589:
471:
I just finished extensive cleaning of refs, including
418:
RFC 9110: HTTP Semantics-Status Codes (rfc-editor.org)
184:
I don't think that's a reliable source because it is
1096:
semantically means unauthenticated not unauthorized.
445:Linking lifewire for rfc definitions? Thats spam
441:Why link random articles instead of official rfc?
956:On multiple places are created the same anchor
425:RFC 9110: HTTP Semantics - 422 (rfc-editor.org)
312:RFC 1945 defines the response line as follows.
1078:Why not attempt it yourself? protected page?
663:Semi-protected edit request on 31 August 2023
8:
916:Semi-protected edit request on 6 April 2024
594:https://en.wikipedia.org/Apache_HTTP_Server
548:Semi-protected edit request on 30 July 2023
204:Semi-protected edit request on 28 June 2021
958:{{anchor|508|Loop Detected|RFC 5842|5842}}
446:
596:(the Apache the article is referring to)
414:RFC 9110: HTTP Semantics (rfc-editor.org)
467:Just finished extensive cleaning of refs
88:509 Bandwidth Limit Exceeded -- sources?
884:2405:8D40:4C78:48EF:44D3:92FF:FEA2:3715
797:
530:Hyper_Text_Coffee_Pot_Control_Protocol
453:2600:1700:CDA0:1060:CF4:7B68:BAC1:185E
44:Do not edit the contents of this page.
7:
120:Sample header for every status code?
244:The word "fulfill" is misspelled.
126:Hypertext_Transfer_Protocol#Sample
24:
1159:
1103:
1003:
923:
882:PANO mag withdrew bat 404 found
815:
734:
670:
612:
555:
512:https://fapsi.be/api/v2/instance
297:webpage display something like:
260:
211:
29:
592:(the Native American tribe) to
590:https://en.wikipedia.org/Apache
386:Updates for release of rfc-9110
787:17:10, 21 September 2023 (UTC)
729:02:19, 19 September 2023 (UTC)
488:Ref count down from 95 to 56.
461:09:18, 30 September 2022 (UTC)
18:Talk:List of HTTP status codes
1:
911:13:52, 18 November 2023 (UTC)
892:01:41, 18 November 2023 (UTC)
542:13:26, 18 December 2022 (UTC)
523:02:51, 15 December 2022 (UTC)
133:I love what am going through
761:request with no discussion.
501:20:23, 6 November 2022 (UTC)
381:15:38, 20 January 2022 (UTC)
157:18:20, 5 December 2020 (UTC)
143:18:18, 5 December 2020 (UTC)
115:00:43, 26 October 2020 (UTC)
1192:18:51, 18 August 2024 (UTC)
1130:to reactivate your request.
1118:has been answered. Set the
960:, instead of proper status
950:to reactivate your request.
938:has been answered. Set the
872:18:36, 6 October 2023 (UTC)
852:01:49, 6 October 2023 (UTC)
771:22:56, 31 August 2023 (UTC)
714:15:57, 31 August 2023 (UTC)
697:to reactivate your request.
685:has been answered. Set the
582:to reactivate your request.
570:has been answered. Set the
436:16:15, 24 August 2022 (UTC)
238:to reactivate your request.
226:has been answered. Set the
1207:
1073:08:07, 30 April 2024 (UTC)
1051:00:16, 23 April 2024 (UTC)
1116:List of HTTP status codes
1031:02:13, 7 April 2024 (UTC)
996:06:47, 6 April 2024 (UTC)
936:List of HTTP status codes
878:PANO mag withdrew bat 404
683:List of HTTP status codes
658:06:55, 31 July 2023 (UTC)
643:10:09, 30 July 2023 (UTC)
606:09:54, 30 July 2023 (UTC)
568:List of HTTP status codes
505:
404:16:10, 22 June 2022 (UTC)
283:00:18, 29 June 2021 (UTC)
254:22:22, 28 June 2021 (UTC)
224:List of HTTP status codes
1177:09:51, 22 May 2024 (UTC)
1153:07:09, 22 May 2024 (UTC)
1037:Please fix a misspelling
361:00:36, 26 Mar 2005 (UTC)
352:23:49, 9 Mar 2005 (UTC)
308:05:13, 8 Mar 2005 (UTC)
198:08:23, 26 May 2021 (UTC)
179:08:14, 26 May 2021 (UTC)
1090:00:03, 3 May 2024 (UTC)
344:19:59, 8 Mar 2005 (UTC)
162:401 unauthorized - cite
515:Bill Evans at Mariposa
42:of past discussions.
1145:Hans Wurst mit Durst
1056:Error 999 - LinkedIn
827:for this alteration
746:for this alteration
837:Edit semi-protected
823:please establish a
756:Edit semi-protected
742:please establish a
372:User:208.240.15.14
1182:@ronaldo saputra
1134:
1133:
964:, etc. Statuses:
954:
953:
821:Not done for now:
740:Not done for now:
701:
700:
586:
585:
463:
451:comment added by
242:
241:
85:
84:
54:
53:
48:current talk page
1198:
1167:
1163:
1162:
1125:
1121:
1107:
1106:
1100:
1083:
1027:
1022:
1011:
1007:
1006:
963:
959:
945:
941:
927:
926:
920:
840:
819:
818:
807:
802:
759:
738:
737:
692:
688:
674:
673:
667:
640:
628:
624:
620:
616:
615:
577:
573:
559:
558:
552:
409:RFC 9110 Updates
366:218 This is fine
268:
264:
263:
233:
229:
215:
214:
208:
81:
56:
55:
33:
32:
26:
1206:
1205:
1201:
1200:
1199:
1197:
1196:
1195:
1160:
1158:
1123:
1119:
1104:
1098:
1081:
1058:
1039:
1029:
1025:
1020:
1004:
1002:
961:
957:
943:
939:
924:
918:
899:
880:
834:
816:
812:
811:
810:
803:
799:
753:
735:
721:178.243.107.156
690:
686:
671:
665:
630:
626:
622:
613:
611:
575:
571:
556:
550:
508:
469:
443:
411:
388:
368:
302:
291:
275:Jochem van Hees
261:
259:
231:
227:
212:
206:
190:Jochem van Hees
164:
122:
90:
77:
30:
22:
21:
20:
12:
11:
5:
1204:
1202:
1184:112.215.200.85
1180:
1179:
1132:
1131:
1108:
1097:
1094:
1093:
1092:
1065:82.212.116.247
1057:
1054:
1038:
1035:
1034:
1033:
1013:
999:
998:
984:
981:
978:
975:
972:
969:
962:{{anchor|509}}
952:
951:
928:
917:
914:
903:49.147.129.138
898:
895:
879:
876:
875:
874:
855:
854:
809:
808:
796:
795:
791:
790:
789:
732:
731:
699:
698:
675:
664:
661:
646:
645:
584:
583:
560:
549:
546:
545:
544:
507:
504:
486:
485:
482:
479:
476:
468:
465:
442:
439:
410:
407:
387:
384:
367:
364:
363:
362:
346:
345:
338:
333:
332:
331:
330:
329:
324:
323:
314:
313:
299:
290:
289:Decimal codes?
287:
286:
285:
240:
239:
216:
205:
202:
201:
200:
186:self-published
163:
160:
147:Betadae music
121:
118:
89:
86:
83:
82:
75:
70:
65:
62:
52:
51:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1203:
1194:
1193:
1189:
1185:
1178:
1174:
1170:
1166:
1157:
1156:
1155:
1154:
1150:
1146:
1143:
1137:
1129:
1126:parameter to
1117:
1113:
1109:
1102:
1101:
1095:
1091:
1088:
1085:
1077:
1076:
1075:
1074:
1070:
1066:
1063:
1055:
1053:
1052:
1048:
1044:
1036:
1032:
1028:
1023:
1018:
1017:
1010:
1001:
1000:
997:
993:
989:
985:
982:
979:
976:
973:
970:
967:
966:
965:
949:
946:parameter to
937:
933:
929:
922:
921:
915:
913:
912:
908:
904:
896:
894:
893:
889:
885:
877:
873:
869:
865:
861:
857:
856:
853:
849:
845:
838:
832:
831:
826:
822:
814:
813:
806:
801:
798:
794:
788:
784:
780:
775:
774:
773:
772:
768:
764:
757:
751:
750:
745:
741:
730:
726:
722:
718:
717:
716:
715:
711:
707:
696:
693:parameter to
684:
680:
676:
669:
668:
662:
660:
659:
655:
651:
644:
641:
638:
634:
629:
619:
610:
609:
608:
607:
603:
599:
595:
591:
581:
578:parameter to
569:
565:
561:
554:
553:
547:
543:
539:
535:
531:
527:
526:
525:
524:
520:
516:
513:
506:I'm a teapot.
503:
502:
498:
494:
489:
483:
480:
477:
474:
473:
472:
466:
464:
462:
458:
454:
450:
440:
438:
437:
433:
429:
426:
421:
419:
415:
408:
406:
405:
401:
397:
393:
385:
383:
382:
379:
378:
373:
365:
360:
355:
354:
353:
351:
343:
342:Lee J Haywood
339:
335:
334:
326:
325:
322:
319:
318:
317:
316:
315:
311:
310:
309:
307:
298:
296:
288:
284:
280:
276:
272:
267:
258:
257:
256:
255:
251:
247:
237:
234:parameter to
225:
221:
217:
210:
209:
203:
199:
195:
191:
187:
183:
182:
181:
180:
176:
172:
169:
161:
159:
158:
154:
150:
145:
144:
140:
136:
131:
128:
127:
124:just like in
119:
117:
116:
112:
108:
104:
101:
97:
94:
87:
80:
76:
74:
71:
69:
66:
63:
61:
58:
57:
49:
45:
41:
40:
35:
28:
27:
19:
1181:
1164:
1138:
1135:
1127:
1112:edit request
1059:
1040:
1015:
1008:
955:
947:
932:edit request
900:
881:
828:
820:
800:
792:
747:
739:
733:
702:
694:
679:edit request
650:27.34.104.17
647:
621:
617:
587:
579:
564:edit request
509:
490:
487:
470:
447:āĀ Preceding
444:
428:45.19.51.146
422:
412:
389:
375:
369:
347:
320:
303:
292:
265:
246:216.81.94.69
243:
235:
220:edit request
165:
146:
132:
129:
123:
105:
102:
98:
95:
91:
78:
43:
37:
36:This is an
1169:Charliehdb
1120:|answered=
940:|answered=
864:Natelolzzz
860:Pinchme123
844:Pinchme123
833:using the
793:References
779:Natelolzzz
752:using the
706:Natelolzzz
687:|answered=
598:Nescio1305
572:|answered=
295:slashdoted
228:|answered=
149:Betadae996
135:Betadae996
825:consensus
744:consensus
627:Paper9oll
534:User94729
271:WP:ENGVAR
79:ArchiveĀ 6
73:ArchiveĀ 5
68:ArchiveĀ 4
60:ArchiveĀ 1
763:PianoDan
449:unsigned
377:Liam McM
266:Not done
493:netjeff
396:netjeff
350:Bawolff
306:Bawolff
171:GrowTHC
39:archive
1087:(talk)
1043:Cjager
988:Kacerd
830:before
749:before
1124:|ans=
1110:This
1016:novov
944:|ans=
930:This
691:|ans=
677:This
576:|ans=
562:This
359:Chris
232:|ans=
218:This
16:<
1188:talk
1173:talk
1165:Done
1149:talk
1069:talk
1047:talk
1009:Done
992:talk
907:talk
888:talk
868:talk
848:talk
783:talk
767:talk
725:talk
710:talk
654:talk
618:Done
602:talk
538:talk
519:talk
497:talk
457:talk
432:talk
400:talk
279:talk
250:talk
194:talk
175:talk
153:talk
139:talk
111:talk
107:mnot
1122:or
1114:to
1084:404
1080:Old
977:644
974:605
971:604
968:509
942:or
934:to
901:B@
689:or
681:to
574:or
566:to
273:. ā
230:or
222:to
188:. ā
1190:)
1175:)
1151:)
1128:no
1082:š©
1071:)
1049:)
1026:c)
1021:(t
1012:ā
994:)
948:no
909:)
890:)
870:)
850:)
839:}}
835:{{
785:)
769:)
758:}}
754:{{
727:)
719:@
712:)
695:no
656:)
637:š
635:ā¢
633:š
604:)
580:no
540:)
521:)
499:)
459:)
434:)
420:.
402:)
374:.
340:ā
281:)
252:)
236:no
196:)
177:)
155:)
141:)
113:)
64:ā
1186:(
1171:(
1147:(
1067:(
1045:(
990:(
905:(
886:(
866:(
858:@
846:(
781:(
765:(
723:(
708:(
652:(
639:)
631:(
623:ā
600:(
536:(
517:(
495:(
455:(
430:(
398:(
277:(
248:(
192:(
173:(
151:(
137:(
109:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.