Title: Protocol mismatch with Raw method
Last modified: August 3, 2018

---

# Protocol mismatch with Raw method

 *  Resolved [Charles Fulton](https://wordpress.org/support/users/mackensen/)
 * (@mackensen)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/)
 * We have a number of sites in a subdomain multisite which, for historical reasons,
   have the site URL in the format [http://foo.baz](http://foo.baz). We force HTTPS
   at the web server level, so the sites are always rendered as [https://foo.baz](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](https://foo.baz),
   the Raw method works.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [John Godley](https://wordpress.org/support/users/johnny5/)
 * (@johnny5)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/#post-10581929)
 * So… it sounds like you solved the problem?
 *  Thread Starter [Charles Fulton](https://wordpress.org/support/users/mackensen/)
 * (@mackensen)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/#post-10586360)
 * It’s a solution, but I think the plugin should have worked in either scenario.
 *  Plugin Author [John Godley](https://wordpress.org/support/users/johnny5/)
 * (@johnny5)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/#post-10586394)
 * 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](https://wordpress.org/support/users/mackensen/)
 * (@mackensen)
 * [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/#post-10590303)
 * 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.

 * ![](https://ps.w.org/redirection/assets/icon-256x256.jpg?rev=983639)
 * [Redirection](https://wordpress.org/plugins/redirection/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/redirection/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/redirection/)
 * [Active Topics](https://wordpress.org/support/plugin/redirection/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/redirection/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/redirection/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Charles Fulton](https://wordpress.org/support/users/mackensen/)
 * Last activity: [7 years, 10 months ago](https://wordpress.org/support/topic/protocol-mismatch-with-raw-method/#post-10590303)
 * Status: resolved