Wrong status code on Nginx server

  • I installed the plugin on WP 3.5 B3 on an Nginx server and created 1 redirect to return a 301 response. Looking at that in Firebug, the URL is in fact redirected but Firebug only shows a 200 response.

    By comparison, the Redirection plugin in most but not all instances shows a 301 status on the old URL and a 200 status on the new one, which seems to be the more correct behavior.

    Thoughts?

    https://www.ads-software.com/extend/plugins/safe-redirect-manager/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    Hey frisco, is this still a problem for you?

    Thread Starter frisco

    (@frisco)

    Thanks for the follow up. Yes, I think it is. I don’t recall whether I tested 1.5 or 1.6, since 1.6 came out right around my comment. But testing 1.6 now on this URL running WP 3.6 alpha…

    https://beta.wpperform.com/sample-page/

    shows a 200 status in Firebug, even though it is redirected with SRM set to a 301. Curiously, this URL:

    https://beta.wpperform.com/sample/

    shows a 301 status. Both redirect to the same place, but only the 1st URL is set up in SRM, and no other re-write plugins are active. In postmeta, the 1st URL does have _redirect_rule_status_code set to 301.

    On same server but different WP install running WP 3.5 and Redirection, a 301 status is returned.

    Hope that helps. If you want more testing, let me know.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Wrong status code on Nginx server’ is closed to new replies.