Support #5152
closed
Question: iframe links allowed on the Commons?
Added by Stephen Klein over 8 years ago.
Updated over 6 years ago.
Description
Trying to add links like:
<iframe src="https://archive.org/embed/JP365-KnowledgeStreamsHD" width="640" height="480" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen></iframe>
but they do not seem to save.
Are iframe links allowed on the Commons? Also, I noticed (based upon a few searches of installed plugins) that the there are no iframe plugins on the Commons.
If iframes are not allowed, we will use the archive-org plugin instead and use, for example:
[archive-org embed=JP365-KnowledgeStreamsHD width=640 height=480 playlist=true]
Thanks,
Stephen
- Status changed from New to Assigned
- Assignee changed from Matt Gold to Boone Gorges
Hi Stephen,
No, iframes are not allowed on the Commons due to the security risks they would open up. However, we routinely create special shortcodes for users to allow them to embed content on their sites; if there is something specific you are interested in embedding, please let us know and Boone can work with you to create a shortcode.
I am running a test crawl on the JP365 site on an individual page now using the archive-org plugin . Let's see how well it works. I will let you know. Thanks.
- Target version set to Not tracked
Hi Stephen - I'm moving this ticket out of a milestone until you've gotten back to us with the results of your tests. Thanks.
Thank you. I changed the seed and I will see if I get better results.
The results are about the same. The same embedded videos did not ingest and worse, the embedded audio did not. Could be the crawler, could be how these were embedded, could be connectivity issues between the crawler and the Commons, but need to know if you think I should continue to define my seed as http rather than https? Thanks.
- Status changed from Assigned to Abandoned
Stephen, sorry for letting your last question lapse. Since you posted it, we have begun to force HTTPS traffic on all *.commons.gc.cuny.edu domains. So it's likely that the http v https distinction is no longer critical for the purposes of the archiving tool (though this too depends on the specifics of the way the archiver handles things like automated redirects). If this continues to be an active problem and you think there's something that might be done on the Commons itself to mitigate, feel free to update this ticket.
Also available in: Atom
PDF