Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using deelay.me will not work from HTTPS #6

Closed
npm1 opened this issue Jan 6, 2020 · 1 comment
Closed

Using deelay.me will not work from HTTPS #6

npm1 opened this issue Jan 6, 2020 · 1 comment

Comments

@npm1
Copy link

npm1 commented Jan 6, 2020

If you try to use an image from deelay.me in an https webpage on Chrome canary (latest chrome version available), it will not work. The DevTools console says "Mixed Content: The page at 'URL' was loaded over HTTPS, but requested an insecure element 'IMAGE'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html". The upgrade to HTTPS doesn't work, and hence the image does not display. Per the blog timeline, this will be the default on February.

@npm1 npm1 changed the title HTTPS images will no longer work Using deelay.me will not work from HTTPS Jan 6, 2020
@biesiad
Copy link
Owner

biesiad commented Jul 18, 2020

Added a certificate. It'll work now.

@biesiad biesiad closed this as completed Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants