Talk:List of HTTP status codes: Difference between revisions

Browse history interactively ← Previous edit Next edit →Content deleted Content addedVisual WikitextInline

Revision as of 09:55, 15 January 2023 editJmccormac (talk \| contribs)Extended confirmed users5,213 edits RV/Undid revision 1133736676 by 103.25.251.242 (talk)Tag: Undo ← Previous edit		Revision as of 23:45, 21 January 2023 edit undo162.19.169.97 (talk) →Semi-protected edit request on 21 January 2023: new sectionTags: Reverted Mobile edit Mobile web editNext edit →
Line 18:		Line 18:
	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 https://fapsi.be/api/v2/instance ] (]) 02:51, 15 December 2022 (UTC)		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 https://fapsi.be/api/v2/instance ] (]) 02:51, 15 December 2022 (UTC)
	: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 ]. 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). ] (]) 13:26, 18 December 2022 (UTC)		: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 ]. 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). ] (]) 13:26, 18 December 2022 (UTC)

			== Semi-protected edit request on 21 January 2023 ==

			{{edit semi-protected\|List of HTTP status codes\|answered=no}}
			] (]) 23:45, 21 January 2023 (UTC)

Revision as of 23:45, 21 January 2023

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.

Put new text under old text. Click here to start a new topic.
New to Misplaced Pages? Welcome! Learn to edit; get help.

Article policies

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 has not yet been rated on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:

Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.

Internet High‑importance

	Internet portal This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Misplaced Pages. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet
High	This article has been rated as High-importance on the project's importance scale.

Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.

Computing High‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Misplaced Pages. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
High	This article has been rated as High-importance on the project's importance scale.

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.

I'm a teapot.

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 https://fapsi.be/api/v2/instance Bill Evans at Mariposa (talk) 02:51, 15 December 2022 (UTC)

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 Hyper_Text_Coffee_Pot_Control_Protocol. 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). User94729 (talk) 13:26, 18 December 2022 (UTC)

Semi-protected edit request on 21 January 2023

It is requested that an edit be made to the semi-protected article at List of HTTP status codes. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

162.19.169.97 (talk) 23:45, 21 January 2023 (UTC)

Categories: