You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
The dashboard could load completely. I tried incognito window andit works. I tried to disable Ublock and Ghostery still dont work. I disable HTTPS everywhere and it worked. So I guess it comes from your extension.
I think the first one is blocked by Ghostery. But as I said even with
Ghostery deactivated it still does not load.
So I think that the problem comes from the third one.
The issue sounds like one that is likely to be caused by mixed content blocking. All such blocking is reported in the web console; could you try out the steps mentioned above to see if you get any warnings or error messages regarding mixed content blocking?
No errors regarding mixed content. I have 4 warnings. 3 are trackers blocked by Ghostery. The other one is this :
XMLHttpRequest cannot load https://www.strikingly.com/a/t/pages/listing.html. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.strikingly.com' is therefore not allowed access.
Thanks for the details. That helped me to get started. It looks like a couple of different things are conspiring to cause issues here: On one hand, there are the CORS issues that you are seeing. It looks like we can partially get rid of those by excluding upgrades for some problematic requests, including the one you saw, and everything under http://www.strikingly.com/s -- then, however, the securecookie in the ruleset will cause the login to break entirely. Removing that, we can finally log in and get half of the dashboard, but even then, a number of CORS related issues persist. These, on the other hand, can be fixed by excluding http://www.strikingly.com/r/v1, as well as all javascript resources fetched from http://assets.strikingly.com.
Thanks for the details. That helped me to get started. It looks like a
couple of different things are conspiring to cause issues here: On one
hand, there are the CORS issues that you are seeing. It looks like we can
partially get rid of those by excluding upgrades for some problematic
requests, including the one you saw, and everything under http://www.strikingly.com/s -- then, however, the securecookie in the
ruleset will cause the login to break entirely. Removing that, we can
finally log in and get half of the dashboard, but even then, a number of
CORS related issues persist. These, on the other hand, can be fixed by
excluding http://www.strikingly.com/r/v1, as well as all javascript
resources fetched from http://assets.strikingly.com.
Activity
jeremyn commentedon Sep 13, 2016
Thanks for the report. Can you please provide a specific URL where you see the problem?
tarbib commentedon Sep 14, 2016
Here we go
http://www.strikingly.com/s#/
http://awesomescreenshot.com/08064kvm4b
jeremyn commentedon Sep 14, 2016
The first link redirects me to a login page. Is an account needed to see the problem?
tarbib commentedon Sep 15, 2016
Yes actually.
On 14 September 2016 at 22:46, Jeremy Nation notifications@github.com
wrote:
Thomas Arbib
France : +33 (0)6 30 66 72 25
中国手机 : +86 156 1056 5007
Twitter : @tarbib http://twitter.com/tarbib
微信 (WeChat) ID : tarbib
http://about.me/thomasarbib
fuglede commentedon Sep 16, 2016
Would you be able to try out the following steps to nail down the issue?
tarbib commentedon Sep 17, 2016
Here we go
I think the first one is blocked by Ghostery. But as I said even with
Ghostery deactivated it still does not load.
So I think that the problem comes from the third one.
On 17 September 2016 at 01:07, Søren Fuglede Jørgensen <
notifications@github.com> wrote:
Thomas Arbib
France : +33 (0)6 30 66 72 25
中国手机 : +86 156 1056 5007
Twitter : @tarbib http://twitter.com/tarbib
微信 (WeChat) ID : tarbib
http://about.me/thomasarbib
fuglede commentedon Sep 17, 2016
tarbib commentedon Sep 19, 2016
Hi,
No errors regarding mixed content. I have 4 warnings. 3 are trackers blocked by Ghostery. The other one is this :
XMLHttpRequest cannot load https://www.strikingly.com/a/t/pages/listing.html. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.strikingly.com' is therefore not allowed access.
fuglede commentedon Oct 9, 2016
Thanks for the details. That helped me to get started. It looks like a couple of different things are conspiring to cause issues here: On one hand, there are the CORS issues that you are seeing. It looks like we can partially get rid of those by excluding upgrades for some problematic requests, including the one you saw, and everything under http://www.strikingly.com/s -- then, however, the
securecookiein the ruleset will cause the login to break entirely. Removing that, we can finally log in and get half of the dashboard, but even then, a number of CORS related issues persist. These, on the other hand, can be fixed by excluding http://www.strikingly.com/r/v1, as well as all javascript resources fetched from http://assets.strikingly.com.tarbib commentedon Oct 10, 2016
oh ok!
Thanks a lot!
On 10 October 2016 at 00:37, Søren Fuglede Jørgensen <
notifications@github.com> wrote:
Thomas Arbib
France : +33 (0)6 30 66 72 25
中国手机 : +86 156 1056 5007
Twitter : @tarbib http://twitter.com/tarbib
微信 (WeChat) ID : tarbib
http://about.me/thomasarbib