问题原文
原帖链接 · DisgruntledGoat · CC BY-SA 3.0
I have a forum where, like most forums, users can post images. I've set up HTTPS across the site, but of course most external images are linked using HTTP, not HTTPS. So loading the forum over HTTPS shows mixed content warnings, etc.
What are some strategies for tackling this problem? Some of the images are from my own site so I can rewrite those URLs to use HTTPS since I know it will work. But for external URLs many don't work with HTTPS so I can't do a blanket rewrite.
I could rewrite non-secure images to links instead of inline images, but that doesn't look great and may be confusing for users. Any better solutions?
已采纳解答
原帖链接 · DisgruntledGoat · CC BY-SA 3.0
Just realised that I never posted my solution. The answer provided in Stephen's comment is what solved it for me. In short, I created a proxy script that does the following:
- If the image is https, leave it alone.
- If the image is http and from a site known to support https (e.g. my own site, imgur.com etc) then rewrite to https.
- Otherwise if the image is http, rewrite it to use
http://example.com/imgproxy?img=ORIGINALURL&hash=KEY
Then the proxy script fetches the HTTP image, caches it locally, and outputs the image data. On repeated requests it outputs the cached data directly. The linked SO answer describes the security hash and other details.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
