I’ve banned query strings (chrismorgan.info)

Article summary

The author has decided to ban unauthorized query strings on their website, citing concerns about tracking and abuse. They argue that adding query strings to URLs without permission is bad manners and can be used to track users. The author's website now returns an error response, specifically a 414 URI Too Long, when a query string is present. This move is intended as a protest against the practice of adding tracking parameters to URLs.

Main themes

• Query strings
• URL tracking
• Web development
• Error handling
• Robustness principle
• Internet etiquette

What commenters say

• The author's decision to ban query strings is a valid response to the problem of tracking and abuse, and serves as a protest against the practice.
• The use of a 414 error response is an abuse of the HTTP standard and goes against the robustness principle.
• The robustness principle, which advocates for being liberal in what you accept from others, is outdated and can lead to security vulnerabilities and vendor lock-in.
• Returning an error response for unauthorized query strings is a reasonable way to handle the issue, as it provides clear feedback to the user and encourages them to correct their behavior.
• Redirecting to the URL with the query string dropped would be a more user-friendly approach than returning an error response.
• The practice of adding query strings to URLs without permission is a form of entitlement and disrespect for the website owner's property.
• The author's approach may not be the most effective way to address the issue, as it may penalize users who are not responsible for the added query strings.
• The robustness principle is not always a good idea, and in some cases, it is better to be strict in what you accept from others to prevent security issues and ensure interoperability.