Cardinalflyer reported a bug where URLs containing %20 (encoded spaces) get incorrectly transformed into %2520 when pasted directly into Discourse, breaking the link. This issue was observed on their instance running Discourse 2.3.9 and mirrored on Meta, where hovering over the link revealed the extra %25 encoding. codinghorror attempted to reproduce the issue but found the link rendered correctly, suggesting the bug may have been previously fixed. Cardinalflyer confirmed that the issue no longer occurs in their current test, acknowledging the fix. The problem appears to stem from how Discourse handles URL encoding during direct pasting versus manual hyperlink insertion, and while users can work around it by using the link insertion tool, the core bug has now been resolved. Cardinalflyer closed the thread with appreciation for the fix.
I swear I’ve seen this discussed here before, but can’t find it, and my instance is doing this (Still? Again?)
When a link which includes an encoded %20 is pasted directly into the text stream, when clicked an extra %25 is added to the front of each %20, making the link invalid.
It does look fixed. If you roll over my link at the start of the topic you’ll see the extra %25’s added. The link you posted in your question doesn’t have them.
I’ll post the link here again to be sure it’s not just something about me…