We’ve created a little search feature for our client (inhaus.webflow.io), and for some reason, when we switched all of the urls to HTTPS, we ran into the following issue:
Mixed Content: The page at 'https://inhaus.webflow.io/product-category/laminate' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://inhaus.webflow.io/search-results'. This request has been blocked; the content must be served over HTTPS.
Our JS has the following, and works perfectly fine if served over HTTP:
Curious though - your last message indicated that removing the trailing slash / fixed the issue for you (or at least from what I inferred from the Russian portion ) - can you confirm that is indeed the case?
@DigitalPanda I think that particular HTTPS → HTTP redirect issue is resolved when you remove the trailing slash, since I’m seeing requests complete fine in DevTools:
I’m not quite sure that the entire response can be wrapped in jQuery like that and traversed - so I suspect it might be a bug in how you’re handling the response once it comes back.