Powerful features, such as Geolocation, capturing user media and a few more are only allowed in secure contexts (valid HTTPS). It has been like that for quite some time and there were many announcements on the Chromium blog
and on ChromeStatus
If you include HTTP resources on HTTPS pages, they might have been automatically upgraded to redirect to the HTTPS variant in order to avoid mixed content (using HTTP within HTTPS), since mixed content is a security risk.
Again, since I am not sure what is you specific and actual problem is, it is hard to help.