• Resolved aetherscythe

    (@aetherscythe)


    Jetpack plugin connects to Jetpack API on http://jetpack.com even when https://jetpack.com is also available

    This should be fixed in the code.
    Here are some more details:

    GET http://jetpack.wordpress.com/jetpack.test/1/ 200 OK-
    HTTP API Transport: curl
    DNS Resolution Time: 0.0121
    Connection Time: 0.0235
    Transfer Start Time (TTFB): 0.1146
    Response Size: 22 B
    Response Content Type: text/plain;charset=utf-8
    IP Address: 192.0.78.33

    Jetpack_Cxn_Tests->test__outbound_http()
    wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-tests.php:379
    Jetpack_Cxn_Test_Base->run_test()
    wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-test-base.php:140
    {closure}()
    wp-content/plugins/jetpack/_inc/lib/debugger/debug-functions.php:56
    WP_Site_Health->perform_test()
    wp-admin/includes/class-wp-site-health.php:175
    WP_Site_Health->enqueue_scripts()
    wp-admin/includes/class-wp-site-health.php:128
    do_action(‘admin_enqueue_scripts’)
    wp-includes/plugin.php:478

Viewing 1 replies (of 1 total)
  • Thread Starter aetherscythe

    (@aetherscythe)

    Nevermind. This happened, simply because the built-in Site Health explicitly checks both http and https. In normal operations the http mode is not being used, AFAICT.

    See here:

    ./public_html/wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-tests.php: $request = wp_remote_get( preg_replace( ‘/^https:/’, ‘http:’, JETPACK__API_BASE ) . ‘test/1/’ );
    ./public_html/wp-content/plugins/jetpack/_inc/lib/debugger/class-jetpack-cxn-tests.php: $request = wp_remote_get( preg_replace( ‘/^http:/’, ‘https:’, JETPACK__API_BASE ) . ‘test/1/’ );

    • This reply was modified 3 years, 4 months ago by aetherscythe.
Viewing 1 replies (of 1 total)
  • The topic ‘Jetpack plugin connects to Jetpack API on http://jetpack.com (not httpS)’ is closed to new replies.