it works fine if you properly escape your urls!

 URIs include components and subcomponents that are delimited by
   characters in the "reserved" set.  These characters are called
   "reserved" because they may (or may not) be defined as delimiters by
   the generic syntax, by each scheme-specific syntax, or by the
   implementation-specific syntax of a URI's dereferencing algorithm.
   If data for a URI component would conflict with a reserved
   character's purpose as a delimiter, then the conflicting data must be
   percent-encoded before the URI is formed.

      reserved    = gen-delims / sub-delims
      gen-delims  = ":" / "/" / "?" / "#" / "[" / "]" / "@"
      sub-delims  = "!" / "$" / "&" / "'" / "(" / ")"
                  / "*" / "+" / "," / ";" / "="

@xuu that’s a joke, right? 😂😂😂 A regular Doe will not know how to do that. Nobody type URLs these days—not that long, anyway. As a comparison, Hugo (a Golang tool) renders those links just fine.

@bender@twtxt.net I think @xuu ’s point is that somehow the URL(s) are wrong in the first place? I went to the Wikipedia page, and copied the URL out of the browser to link to here – Let’s see 👈 Already as I’m typing this I see a problem :/ [here](https://en.wikipedia.org/wiki/Tories_(British_political_party))

I find it interesting too, this is obviously such a problem that Wikipedia have two URLs for this page:

https://en.wikipedia.org/wiki/Tories_(British_political_party)

and

https://en.wikipedia.org/wiki/Tories_(British_political_party

Do browsers not percent-encode URLs automatically? They did in the past, right? For some reason I thought they still did, but they showed the original URL in the bar for readability.

I just used mitmproxy and pasted that URL and it didn’t escape it at all.

I swear I copied a URL from an address bar one time and I noticed it was percent encoded on the clipboard when the text in the box wasn’t. It was showing me something easy to read, but when I was going to use that URL for something else it was properly encoded so it wouldn’t cause exactly this type of problem.

mitmproxy is not un-escaping for readability: