This is an old revision of this page, as edited by Jamedeus (talk | contribs) at 00:44, 8 May 2024 (Undid revision 1222793884 by 2804:6E30:801A:8030:7DB1:F3C8:20D8:2978 (talk)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 00:44, 8 May 2024 by Jamedeus (talk | contribs) (Undid revision 1222793884 by 2804:6E30:801A:8030:7DB1:F3C8:20D8:2978 (talk))(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)This is the talk page for discussing improvements to the List of HTTP status codes article. This is not a forum for general discussion of the article's subject. |
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1, 2, 3, 4, 5, 6Auto-archiving period: 30 days |
This article is written in British English, which has its own spelling conventions (colour, travelled, centre, defence, artefact, analyse) and some terms that are used in it may be different or absent from other varieties of English. According to the relevant style guide, this should not be changed without broad consensus. |
This article is rated List-class on Misplaced Pages's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
|
Please fix a misspelling
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 Cjager (talk) 00:16, 23 April 2024 (UTC)
Error 999 - LinkedIn
I suggest to add the following unofficial status code that puzzled some developers. The code was generated by LinkedIn. For more info, see: https://learn.microsoft.com/en-us/archive/msdn-technet-forums/5a4f8eb5-bf1b-4776-b4bb-4baef621838f 82.212.116.247 (talk) 08:07, 30 April 2024 (UTC)
- Why not attempt it yourself? protected page? Old💩404 (talk) 00:03, 3 May 2024 (UTC)