Title: BUG – HTTPS requested an insecure XMLHttpRequest endpoint Last modified: June 22, 2018 --- # BUG – HTTPS requested an insecure XMLHttpRequest endpoint * Resolved [mabrams](https://wordpress.org/support/users/mabrams/) * (@mabrams) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/) * I have a new WP install with theme Twenty Seventeen and no active plugins. The chrome browser developers console is reporting an insecure XMLHttpRequest endpoint * My https site is trying to include http content via function.js [http://webcache.googleusercontent.com](http://webcache.googleusercontent.com) this needs to be [https://webcache.googleusercontent.com](https://webcache.googleusercontent.com) * I don’t know how to fix it. This error is found on a number of WP sites I’m looking at, so its not my server or install. * I believe its a WP bug. * Thanks for your support. * FULL CONSOLE ERROR MESSAGE * JQMIGRATE: Migrate is installed, version 1.4.1 functions.js:33 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check [https://xhr.spec.whatwg.org/](https://xhr.spec.whatwg.org/). file_get_contents @ functions.js:33 functions.js:34 Mixed Content: The page at‘ [https://test.sunlakesofarizona.com/’](https://test.sunlakesofarizona.com/’); was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘[http://webcache.googleusercontent.com/search?q=cache:https://test.sunlakesofarizona.com/’](http://webcache.googleusercontent.com/search?q=cache:https://test.sunlakesofarizona.com/’);. This request has been blocked; the content must be served over HTTPS. file_get_contents@ functions.js:34 2VM134 functions.js:34 Mixed Content: The page at ‘[https://test.sunlakesofarizona.com/’](https://test.sunlakesofarizona.com/’); was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘[http://webcache.googleusercontent.com/search?q=cache:https://test.sunlakesofarizona.com/’](http://webcache.googleusercontent.com/search?q=cache:https://test.sunlakesofarizona.com/’);. This request has been blocked; the content must be served over HTTPS. file_get_contents@ VM134 functions.js:34 getResults @ VM134 functions.js:83 (anonymous) @ VM134 functions.js:152 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fbug-https-requested-an-insecure-xmlhttprequest-endpoint%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 5 replies - 1 through 5 (of 5 total) * [te_taipo](https://wordpress.org/support/users/te_taipo/) * (@te_taipo) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10424271) * Have you made any custom edits to the Twenty Seventeen theme? * Thread Starter [mabrams](https://wordpress.org/support/users/mabrams/) * (@mabrams) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10426265) * No changes – test your own – If you look at your own WP page with the Google Chrome browser, select any text on the page and right click for the pop menu, then select the bottom option -> Inspect * This will open the Chrome (Developer Tools) inspector. Not the errors red circle X. Click the Console menu option on the Developer Tool header (mine is docked to the bottom of the page). * WP is including some legacy code that was hard coded for http – I needs to be modified to detect the protocol and use https or http based on the host. This solves the error. * Even thought the page works with errors, it takes a performance hit as the content is blocked. * The code should be fixed. * Thread Starter [mabrams](https://wordpress.org/support/users/mabrams/) * (@mabrams) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10426268) * The theme is not the issue – this is core WP. * WP Developers should resolve this. * The warning flag, which will become another error states: Synchronous XMLHttpRequest outside of workers is in the process of being removed from the web platform as it has detrimental effects to the end user’s experience. (This is a long process that takes many years.) Developers must not pass false for the async argument when current global object is a Window object. User agents are strongly encouraged to warn about such usage in developer tools and may experiment with throwing an “InvalidAccessError” DOMException when it occurs. * [te_taipo](https://wordpress.org/support/users/te_taipo/) * (@te_taipo) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10427003) * I am unable to replicate this in my default install of Chrome and default install of wordpres/twentyseventeen sorry. * Perhaps someone else may have more success, i.e in finding function.js * You could also report this as a bug here [https://core.trac.wordpress.org/newticket](https://core.trac.wordpress.org/newticket) * Thread Starter [mabrams](https://wordpress.org/support/users/mabrams/) * (@mabrams) * [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10427272) * Thank you. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘BUG – HTTPS requested an insecure XMLHttpRequest endpoint’ is closed to new replies. * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 5 replies * 2 participants * Last reply from: [mabrams](https://wordpress.org/support/users/mabrams/) * Last activity: [8 years, 3 months ago](https://wordpress.org/support/topic/bug-https-requested-an-insecure-xmlhttprequest-endpoint/#post-10427272) * Status: resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics