On 06/26/2015 06:44 AM, Amos Jeffries wrote:
On 26/06/2015 7:55 a.m., Alex Rousskov wrote:
Tokenizer cannot handle URIs with whitespaces directly, like your patch
attempts to do: Tokenizer alone cannot handle ambiguous grammars. To
handle such URIs well, you have two options IMO:
A. The old
Sure.
Changed the trunk matrix build to match.
I've also changed the website-tarballs-latest and website-tarballs-head
jobs so that they are triggered by a successful matrix build instead of
autonomously polling (and possibly failing the build). Please let me know
if you wish me to revert this.
On 26/06/2015 7:55 a.m., Alex Rousskov wrote:
On 06/25/2015 08:13 AM, Amos Jeffries wrote:
Which is why I want to go the route of HTTP/0.9 handling. Its
clear when products encounter it and cause themselves problems.
Sigh. You are repeating essentially the same argument as before. Any
let's
