Timeline for Printmaker fails to render images under SSL
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 26, 2017 at 18:52 | comment | added | Damon | I am pulling from an S3 prefix, so each image is using a fully qualified url (also https). Everything works great when the site is http. Even pulling https images into http works great. As soon as I force https, the wheels come off. Forcing http on that specific url may be my only option. Just gotta figure out how to do that. :) | |
Jun 26, 2017 at 15:47 | comment | added | SamC | Was working on a PDF thing this morning, and debugging a similar issue in chrome. It doesn't like relative links for images. "/images/myimage.png" gave the 'image not found error' - making it an absolute url "mysite.com/images/myimage.png" worked. | |
Jun 23, 2017 at 21:53 | comment | added | Damon | Yep! makes sense to me. Turns out its the actual image(s) that are causing the problem. | |
Jun 23, 2017 at 19:57 | comment | added | SamC | Well, firefox will display mixed http & https content with an error over the lock. Whereas chrome won't load the non-https stuff at all. I was suggesting that if chrome won't show an image from S3, it's an http/https setting. If chrome does show an image from the S3, it's something more specific to chrome. that make more sense? | |
Jun 23, 2017 at 19:26 | comment | added | Damon | Yep! Everything works great otherwise - Firefox even renders the PDF. | |
Jun 23, 2017 at 19:01 | comment | added | SamC | Ah. I haven't used S3 much via SSL - Can you get images to load on an https page from that S3 bucket? | |
Jun 23, 2017 at 18:54 | history | edited | SamC | CC BY-SA 3.0 |
added a note about chrome vs firefox
|
Jun 23, 2017 at 15:00 | comment | added | Damon |
Hi SamC - all of the assets are coming from an S3 prefix. I've made sure to set all of the S3 url's to include https . I did not have the site settings to include https. I tried but got the same result. "Failed to load PDF". Odly enough, Firefox works...
|
|
Jun 23, 2017 at 14:13 | history | answered | SamC | CC BY-SA 3.0 |