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…

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

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
External Link- Encode Problem Get Help	1	153	May 8, 2023
“Invalid character in header content [“authorization”]” External Collections, Custom Actions & Collections	3	703	December 21, 2021
External URL - Redirect Problem Get Help	3	160	May 22, 2023
External link after custom action is only working on desktop PWA, not mobile PWA? Get Help	2	384	December 26, 2022
PDF generator api component integration 422 error External Collections, Custom Actions & Collections	10	369	August 10, 2022