# https 环境下 onebox 中 favicon 的问题 **URL:** \ **Category:** Support\ **Created:** [2018年二月20日 14:40 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035 "2018-02-20T14:40:53Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![Vaping\_Community](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vaping_community/32/89248_2.png) [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)\ **Post date:** [2018年三月14日 22:01 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/21 "2018-03-14T22:01:43Z")
I’m not using that plugin, any reason why my topic name was edited @codinghorror ?? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2018年三月14日 22:40 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/22 "2018-03-14T22:40:17Z")
I need @techapj to weigh and and see if he can duplicate this or not, first. ---
**Author:** ![Vaping\_Community](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vaping_community/32/89248_2.png) [@Vaping\_Community](https://meta.discourse.org/u/Vaping_Community)\ **Post date:** [2018年三月14日 22:47 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/23 "2018-03-14T22:47:03Z")
My initial topic (.ico in one box breaks https) was solved, I had to add ico to extensions so discourse could download them. This new topic name should have its own topic not sure why @pfaffman edited the first time, maybe revert and split @ post 12? ---
**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\ **Post date:** [2018年三月15日 02:01 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/25 "2018-03-15T02:01:53Z")
This issue is not due to the TLP plugin (the topic title needs updating). For example, you can see it currently on @adorfer’s site [here](https://forum.freifunk.net/t/rp-artikel-freifunk-kollidiert-mit-jugendschutz/16224), even though TLP is disabled. Also, I’ve added the offending links on @adorfer’s site (German newspaper websites need to migrate to https 🙂 ) to my sandbox and the .ico download behaviour (and https) works normally. See further here: [https://discourse.angusmcleod.com.au/c/tlp](https://discourse.angusmcleod.com.au/c/tlp) The reason you were seeing some difference between [safe mode](https://meta.discourse.org/t/53504?silent=true) and normal mode on that site is because TLP just replicates the existing issue with the .ico images in the topic list (in addition to the individual topics in which the issue occurs). For anyone else who has an issue with favicon’s in oneboxes breaking https, there are five site settings that will affect whether a remote image is downloaded to Discourse, including favicon (`.ico`) images. You need to check all of them: - `download remote images to local` - `download remote images threshold` - ` download remote images max days old` - ` disabled image download domains` - ` authorized extensions` You need to rebake (‘rebuild html’) any post with an offending image to re-trigger the job that pulls hotlinked images once you’ve updated any of these settings. After you’ve rebuilt the html, the job will run after however many seconds you’ve set as the `editing grace period` in your site settings (Default is 300 seconds, i.e. 5 mins). You can see the progress of the job at `yoursite.com/sidekiq`, it’s called “PullHotlinkedImages” e.g. ![Screenshot%20at%20Mar%2015%2008-55-02](https://global.discourse-cdn.com/meta/original/3X/d/d/dda0327a9c087292acc90b81c9f3d9403b406d80.jpg) Only once all of the above settings are set appropriately and this job has fully completed should you expect to see Discourse serving a local version of the hotlinked image, and any associated https issues resolve. ---
**Author:** ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)\ **Post date:** [2018年三月15日 07:13 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/26 "2018-03-15T07:13:21Z")
The original issue reported by @Vaping_Community was due to favicons in onebox using `http` links, and @Falco provided a solution to fix it. @adorfer was not able to fix this issue by using Rafael’s solution, and the site was working fine in [safe mode](https://meta.discourse.org/t/53504?silent=true) so assumed that “Topic List Previews” plugin was the culprit. But as explained by @angus in detail above, there are few more settings that needs to be changed in order to download all onebox images locally. So this issue happens only when Onebox tries to load unsafe (non `https`) images, and can be fixed by downloading images locally by modifying settings as specifed by Angus above. ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2018年三月15日 07:28 UTC](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035/27 "2018-03-15T07:28:29Z")
[上一頁](https://meta.discourse.org/t/problem-with-https-with-favicon-in-onebox/81035.md?page=1)