Remove status code 11 SENSITIVE INPUT
To summarize a discussion on IRC:
- There is no way for a client or server to know whether a URL contains sensitive information or not. This complicates displaying the URL on the client side and logging requests on the server side.
- We shouldn't encourage putting sensitive information in URLs. URLs are meant to be shared, and putting sensitive information in them is potentially dangerous. URLs can also be stored in browser history and cache, user bookmarks, server logs, etc.
- There doesn't seem to be a pressing need for them. Client certificates should cover the majority of use cases.
According to gemini://gemini.bortzmeyer.org/software/lupa/stats.gmi, there are 1,573 occurrences of status code 10 but no occurrences of status code 11.
Edited by Ghost User