Should there be an HTTP error code for censorship? Quite probably and I agree with Terence that 403 (forbidden) is a misleading response. I really like his various proposals and the format he uses is actually a decent quick overview of the HTTP response header categorisation (1xx, 2xx, etc.) as well. Personally, if the 450 response is widely accepted and considered a standard for parental controls then I really, really love 451. It's a great reference and a useful response header. However, I do agree with a lot of the comments that it doesn't feel like censorship should be bracketed in with the 4xx category. It also looks like the proposal has been rejected or is possibly just stalled.
- Source
- Link to Original 🔗
- Published
- Categories
- Frontend, The World Wide Web
- Tags
- HTTP, response, 451, censorship, proposal
Explore Other Notes
⬅ Newer
Micro-interactions for powerful design
A useful and well-written overview of micro-interactions and how they can take a design from good to great. Includes some excellent examples of animated buttons, swipe interactions, and more from …
Older ➡
New Zealand bird identification
A frankly excellent website for identifying bird species, particularly useful if you're like me and trying to do so years after having seen them 😁 It's a really neat interface that makes narrowing …
- <!DOCTYPE html> <html> <head> <title></title> </head> <body> <p>Should there be an HTTP error code for censorship? Quite probably and I agree with Terence that 403 (forbidden) is a misleading response. I really like his various proposals and the format he uses is …</p> </body> </html>
- Murray Champernowne
