Having an encoded forward slash (%2F) in a URL doesn’t seem to work with an External Link action. It appears to be double encoding the forward slash and replacing %2F with %252F in the URL. The consequence is that you obviously can’t access your external content. This is a major problem for me right…

Following up on this post that our dev team has had a chance to look over this and it isn’t a simple solution. There are quite a few factors in place and avenues of pros/cons to go down. The product team at large will be having a discussion on this in the new year 2021 to talk through the right opti…

External Link - Forward slash being double encoded (%2F to %252F)

Get Help

anon78309838 October 12, 2020, 9:49am 2

Thanks for pointing this out. This is definitely a bug on our side. I have submitted it to the team.

Forward slash being double encoded (%2F to %252F)

Topic		Replies	Views
Forward slash being double encoded (%2F to %252F) Get Help	1	361	December 21, 2020
External Link- Encode Problem Get Help	0	205	April 28, 2023
External URL - Redirect Problem Get Help	2	228	May 12, 2023
Is there a solution to %2F URL encoding? Get Help	4	1201	December 15, 2021
Altered URL on published app Get Help	8	590	November 16, 2021

External Link - Forward slash being double encoded (%2F to %252F)

Related topics