wp_should_replace_insecure_home_url

The timeline below displays how wordpress function wp_should_replace_insecure_home_url has changed across different WordPress versions. If a version is not listed, refer to the next available version below.

WordPress Version: 5.7

/**
 * HTTPS migration functions.
 *
 * @package WordPress
 * @since 5.7.0
 */
/**
 * Checks whether WordPress should replace old HTTP URLs to the site with their HTTPS counterpart.
 *
 * If a WordPress site had its URL changed from HTTP to HTTPS, by default this will return `true`, causing WordPress to
 * add frontend filters to replace insecure site URLs that may be present in older database content. The
 * {@see 'wp_should_replace_insecure_home_url'} filter can be used to modify that behavior.
 *
 * @since 5.7.0
 *
 * @return bool True if insecure URLs should replaced, false otherwise.
 */
function wp_should_replace_insecure_home_url()
{
    $should_replace_insecure_home_url = wp_is_using_https() && get_option('https_migration_required') && wp_parse_url(home_url(), PHP_URL_HOST) === wp_parse_url(site_url(), PHP_URL_HOST);
    /**
     * Filters whether WordPress should replace old HTTP URLs to the site with their HTTPS counterpart.
     *
     * If a WordPress site had its URL changed from HTTP to HTTPS, by default this will return `true`. This filter can
     * be used to disable that behavior, e.g. after having replaced URLs manually in the database.
     *
     * @since 5.7.0
     *
     * @param bool $should_replace_insecure_home_url Whether insecure HTTP URLs to the site should be replaced.
     */
    return apply_filters('wp_should_replace_insecure_home_url', $should_replace_insecure_home_url);
}