How should clients handle question marks in the path portion of hyper URLs?
Currently, if we don't encode question marks, the portion after the question mark is treated as a search query and removed. If we do encode question marks, we get %3F back from GET requests instead of question marks.
How should clients handle question marks in the path portion of hyper URLs?
Currently, if we don't encode question marks, the portion after the question mark is treated as a search query and removed. If we do encode question marks, we get
%3Fback fromGETrequests instead of question marks.Demonstrated in #70.