- This topic has 1 reply, 2 voices, and was last updated 14 years, 3 months ago by
.
-
Posts
-
We are selling a recording that is hosted by webex. The link is of the form https://domain.webex.com/company/lsr.php? followed by a parameter string.
When the encrypted link is clicked the webpage opened shows a 302 moved with the real decoded link. Is there a way to prevent this?
http://www.checkupdown.com/status/E302.html
“…If your client is not a Web browser, it should behave in the same way as a Web browser i.e. immediately retry the alternative URL.”
The WebEx client is not behaving properly.
With that said, I suppose that if you place the download file on Amazon S3, and deliver the encrypted link using the eStore S3 integration feature, either it would work the way it should or at worse display the expiring URL request for the S3 object; which is “safe” to disclose.
- You must be logged in to reply to this topic.