Timeline for HTTP result code tags
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 11, 2020 at 10:00 | history | edited | CommunityBot |
Commonmark migration
|
|
Apr 27, 2012 at 19:58 | comment | added | Ellie K | The tags for 404 and http-status-code-404 need to be cleaned up. I would go with 404. Right now, there are questions with one or both those tags. I'll manually clean, just tell me your preference. 403 should remain, as it is important (403 is Forbidden) in my opinion. | |
Mar 31, 2012 at 23:13 | history | edited | the-wabbit | CC BY-SA 3.0 |
added 740 characters in body
|
Mar 28, 2012 at 18:48 | comment | added | the-wabbit | I would argue that a status/response code of whatever kind is a bad candidate as a crouping criterion, thus making it a bad tag. so http-status-code-whatever would also need retagging IMO. | |
Mar 28, 2012 at 3:05 | comment | added | Andrew | If these were the only tag on a question, it would be ruled off-topic or useless; burnination time. | |
Mar 28, 2012 at 0:16 | comment | added | jscott | @Ladadadada There also exists http-status-code-404, http-status-code-403 and http-status-code. Thoughts? | |
Mar 27, 2012 at 16:06 | comment | added | Ladadadada | Would http-303 be more useful as a tag than just 303? | |
Mar 27, 2012 at 12:17 | comment | added | John Gardeniers | Useless yes but too localised? These codes are used globally by any even half-decent web server. How much more non-localised can you get? | |
Mar 27, 2012 at 11:02 | comment | added | Tom O'Connor | Entirely useless, and also [too-localized] | |
Mar 27, 2012 at 10:12 | history | edited | the-wabbit | CC BY-SA 3.0 |
edited title
|
Mar 27, 2012 at 9:55 | history | asked | the-wabbit | CC BY-SA 3.0 |