-
-
Notifications
You must be signed in to change notification settings - Fork 936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not enforce URLs to be UTF-8 #2208
Comments
It is correct that URI schemes created before 2005 are not affected; however this would require the It is worth distinguishing that URIs are not URLs but URLs are URIs, so calling However, in most cases URLs represent letters and not raw bytes, so the push for UTF-8 is very understandable. On a side note, I (and surely tens of others) have spent days over the course of being here, and still got http: URI encoding wrong. I acknowledge the mistake. |
What would you like to discuss?
While trying to make an announce as per the bittorrent spec, I encountered an error. In the bittorrent announce (https://www.bittorrent.org/beps/bep_0003.html), the
info_hash
param is the raw 20 byte hash, which needs to be escaped (for non URL safe characters / arbitrary octets), and is currently being blocked by Got, due to a call to "decodeURI()":got/source/core/options.ts
Line 1406 in e24b896
Error Trace
Related Issue
I've found a related issue, which seems to be incorrectly closed: #420 (comment) , which says
However, from my understanding, the requirement applies to new URI schemes created after 2005 (last paragraph of https://www.rfc-editor.org/rfc/rfc3986#section-2.5) , so for HTTP it is not be a requirement.
For clarification I contacted the IETF via their mailing list, and Julian R. (co-author of HTTP specifications) confirmed this (ref: https://mailarchive.ietf.org/arch/msg/ietf/0OydNWKPkHCsDE-z1N5rILhQBYo/) . In fact he even commented in the original issue
Based on this, would you be open to removing this restriction, which goes against the spec?
Seems this MR is related: #2200
The text was updated successfully, but these errors were encountered: