Viewing 5 replies - 1 through 5 (of 5 total)
  • Have you made any custom edits to the Twenty Seventeen theme?

    Thread Starter mabrams

    (@mabrams)

    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

    (@mabrams)

    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.

    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

    Thread Starter mabrams

    (@mabrams)

    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.