# CORS issue on meta
**URL:** https://meta.discourse.org/t/cors-issue-on-meta/29863
**Category:** Site feedback
**Created:** [June 10, 2015, 6:22pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863 "2015-06-10T18:22:51Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [June 10, 2015, 6:22pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/1 "2015-06-10T18:22:52Z")
I wasn’t getting a green lock on meta - turned out to be that I visited a topic with mixed content, but I see that this is happening on meta:
> Image from origin ‘[https://cdn-enterprise.discourse.org/meta](https://cdn-enterprise.discourse.org/meta)’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘[https://meta.discourse.org](https://meta.discourse.org)’ is therefore not allowed access.
Figured I’d let someone know.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [June 10, 2015, 7:06pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/2 "2015-06-10T19:06:05Z")
Yeah this often happen with oneboxed content or linked images. There’s not much we can do here.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 10, 2015, 7:12pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/3 "2015-06-10T19:12:03Z")
Wouldn’t that header be present on the Fastly content @sam?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [June 10, 2015, 7:13pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/4 "2015-06-10T19:13:27Z")
The mentioned warning (in Chrome console) shows up on the main page, so I don’t think it has anything to do with oneboxed content or linked images.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [June 10, 2015, 7:16pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/5 "2015-06-10T19:16:46Z")
Agreed Regis.. it was foreign content in a topic that got my attention.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 10, 2015, 7:19pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/6 "2015-06-10T19:19:20Z")
not really, we have to enable cors to get headers, not sure why this is happening but I also dislike the errors in chrome.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [June 27, 2015, 3:57pm UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/7 "2015-06-27T15:57:35Z")
This is happening when “Show new / updated topic count on browser icon” is enabled in the user preferences. The missing `Access-Control-Allow-Origin` header on S3 prevents the topic count to show up in the favicon.
>
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [August 11, 2015, 8:43am UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/8 "2015-08-11T08:43:12Z")
Since the topic about [Favicon notification](https://meta.discourse.org/t/favicon-notification/7427/24) was closed as “complete” I’d like to point out, that there’s still an issue with CORS that can prevent it from working properly.
> [@gerhard](#):
>
> The missing Access-Control-Allow-Origin header on S3 prevents the topic count to show up in the favicon.
I guess this should be mentioned in some documentation about S3 **and** it would be great if this header could be enabled here on meta. 😉
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 11, 2015, 8:55am UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/9 "2015-08-11T08:55:02Z")
Maybe do a howto on it?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [August 11, 2015, 10:03am UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/10 "2015-08-11T10:03:10Z")
I’m not a S3 user. Maybe we should move this out of Lounge in order to find someone willing to document this?
Anyway, the solution posted on [stackoverflow](http://stackoverflow.com/questions/17533888/s3-access-control-allow-origin-header) looks promising…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 25, 2015, 2:21am UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/11 "2015-08-25T02:21:11Z")
Fixed everywhere (including for S3 setups per: [https://meta.discourse.org/t/whatever-happened-to-favicon-notifications/32351/8?u=sam](https://meta.discourse.org/t/whatever-happened-to-favicon-notifications/32351/8))
Yay 🎊
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 25, 2015, 2:21am UTC](https://meta.discourse.org/t/cors-issue-on-meta/29863/12 "2015-08-25T02:21:16Z")