Hi folks -
...
Our Swift URLs (which are based on RFC 1808) fail to instantiate with these unencoded fragments. This led to some cross-team discussion on
T307603 about where and how to fix this. Does this seem like something that could (or should) be fixed deeper within MediaWiki? Can we encode the fragments of urls in the response of any MediaWiki API?
@matmarex did some excellent investigation in
this comment, and it sounds like the original Chrome bug that led to this unencoded fragment need within MediaWiki is no longer an issue. We're open to fixing it client-side if this proposal is a no-go, but I wanted to make sure we weren't putting in a client-side workaround for a server-side workaround that is no longer needed. I appreciate any thoughts!