Protocol mismatch with Raw method

  • Resolved Charles Fulton

    (@mackensen)


    6 years, 1 month ago

    We have a number of sites in a subdomain multisite which, for historical reasons, have the site URL in the format http://foo.baz. We force HTTPS at the web server level, so the sites are always rendered as https://foo.baz. For (probably) unrelated reasons we need to use the Raw method for the REST API instead of default method. In this situation, with the URL mismatch and the Raw method, the plugin does not work. If we change the site URL to https://foo.baz, the Raw method works.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Godley

    (@johnny5)

    6 years, 1 month ago

    So… it sounds like you solved the problem?

    Thread Starter Charles Fulton

    (@mackensen)

    6 years, 1 month ago

    It’s a solution, but I think the plugin should have worked in either scenario.

    Plugin Author John Godley

    (@johnny5)

    6 years, 1 month ago

    The plugin has different API methods because some WordPress setups block the API in various different ways. In your case it seems it is because you have different protocols for your WordPress URL settings and this triggers the browser’s security feature which prevents the API being accessed at a http address when loaded over https. Alternatives are provided to get around this setup.

    Note this isn’t specific to Redirection, and will affect any plugin that uses the REST API.

    Thread Starter Charles Fulton

    (@mackensen)

    6 years, 1 month ago

    Thanks, that makes sense.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Protocol mismatch with Raw method’ is closed to new replies.