Timeline for Mixed Content: The page at was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 13, 2018 at 14:16 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jun 13, 2018 at 14:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
May 14, 2018 at 13:14 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Apr 14, 2018 at 12:33 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Mar 14, 2018 at 13:59 | answer | added | user1069816 | timeline score: 1 | |
Mar 2, 2018 at 0:39 | comment | added | jammykam | Sorry, no idea where that port number is coming from, never seen that issue before. Check your config and make sure it is not specified somewhere. | |
Mar 1, 2018 at 19:56 | comment | added | Naveed Ahmad | I added both the scheme="https" and the CSP recommendations as mentioned by @jammykam and Michael West . Now I get the second URL with https but with port number and is timing out. We do have a blank http to https rule setup for all. 'cms.mydomain.org:8003/sitecore/shell/~/xaml/… | |
Feb 27, 2018 at 17:02 | comment | added | George Chang |
Are you rewriting your URLs? The intermediary requests won't pick up on the HTTPS since it's probably using the LinkManager to generate the URL. I would look into @jammykam's recommendation above on setting scheme="https" on your Sitecore site or use the URL Rewrite module to rewrite all HTTP requests to be HTTPS.
|
|
Feb 26, 2018 at 21:16 | comment | added | Michael West | Does this answer help? sitecore.stackexchange.com/a/10427/95 I found that I needed to change the CSP for Chrome to allow the request. | |
Feb 26, 2018 at 21:03 | comment | added | jammykam |
Do you have scheme="https" attribute set on your <site> node in config?
|
|
Feb 26, 2018 at 20:51 | history | asked | Naveed Ahmad | CC BY-SA 3.0 |