Closed andylolz closed 10 years ago
This is really hacky! The browser check is there because I’ve no idea how this will behave across browsers. (Also because this breaks the tests (expecting 200, got 302) without updating them with non-breaking spaces, which I’d rather not do.)
@andylolz i think we need to revert this change as it is a breaking one :-( e.g. this url which has a %20 in the url now breaks
It breaks because your "breaking space" fixer now strips out %20 in url which is essential.
We can add a test ;-)
Aha ok, that’s not too bad… I guess if we just leave URLs alone that should sort it.
Chrome makes URLs with spaces illegible:
We replace these %20s with non-breaking spaces (which look normal) and then parse them as if they were spaces.
Refs #87.