%2F in hash fragment causing 404 when loading iFrame
Posted: Tue Dec 06, 2016 11:40 pm
Hi - I'm chasing down a problem that our users have been seeing when clicking links in Slack and some email clients. We have URLs such as
When I paste this into Slack, it looks just the same, but clicking it sends a different URL to the browser:
This results in a 404 in the 'content' iframe. What seems to be happening is that Slack is, correctly, percent-encoding special characters in the hash fragment.
Looking at toc-driver.js, the loadiframe function replaces %23 with #, but does not replace %2F with /. I did a quick local test, and replacing line 152
with
fixes things. Should we make this change in toc-driver.js on our server?
Code: Select all
https://streamsets.com/documentation/datacollector/latest/help/#Getting_Started/What_is_DataCollector.html#concept_sjz_rmx_3q
Code: Select all
https://streamsets.com/documentation/datacollector/latest/help/#Getting_Started%2FWhat_is_DataCollector.html%23concept_sjz_rmx_3q
Looking at toc-driver.js, the loadiframe function replaces %23 with #, but does not replace %2F with /. I did a quick local test, and replacing line 152
Code: Select all
dynamicURL = dynamicURL.replace(/%23/g,'#');
Code: Select all
dynamicURL = dynamicURL.replace(/%23/g,'#').replace(/%2F/ig,'/');