Relative links to media break when HTML files become too large

eric_orton
Community Contributor

I have a course that, for a number of reasons, includes several HTML files that are inserted into native Canvas content pages using an <iframe>. These HTML files are in the course files, and include relative paths to media included on the HTML page (such as images, Flash, CSS stylesheets, JavaScript files, etc.), which are also in the course files. For most of the HTML files, this works great.

One particular file, though, has a lot of content -- so much that the HTML file is over 130 KB. That seems to be the threshold at which Canvas changes where the HTML file is stored, which means that none of the relative paths in the file work anymore. Thus, styles are wrong, images don't show, etc.

Specifically, HTML files over 130 KB get stored at:

https://instructure-uploads.s3.amazonaws.com/account_74070000000000001/attachments 

Smaller HTML files and all the media files get stored at:

https://cluster45-files.instructure.com/courses/7407~1028/files/7407~129638/course files

Does anyone know of a way to solve this problem, like perhaps a setting where we can prevent Canvas from moving designated files to other cloud storage or set a higher threshold for storing HTML files in this other cloud storage?

By the way, I've already thought of breaking the HTML file into two files, each under 130 KB. But, for the sake of continuity as well as to better understand how Canvas works, I'd like to get an answer to this question before deciding to go that route.

Eric

Labels (1)