Hi James, thank you very much for your patience!
> > > Granted, the assert is new but it's just asserting the contract of the > > > APIs. The URIs were always supposed to be canonicalized. > > Yeah, and I even have code that deals with a slash at the end and so on. > > > > The other idea is that the requirements have changed - perhaps an UTF8 URL > > like > > file:///tmp/fsvs-test-1044/repos/trunk/ä-30305/ö-13157/§-2186 > > isn't allowed anymore, but the non-ASCII characters have to be encoded? > > From what I can tell, that was always supposed to be the case. What was? That non-ASCII needs to be encoded? I thought that the API is defined for UTF8-strings, so I can understand about using urlencode for [%\/?&] - but for "normal", printable UTF8 characters? > I'm inclined to close this as the API being used incorrectly. So, I should just make FSVS pass eg. "ö" as "%C3%B6" instead?
