301 redirect

  • Resolved bernardberry646

    (@bernardberry646)


    5 years, 2 months ago

    Your plugin warns:
    WordPress 301 redirect enabled. We recommend to enable a 301 .htaccess redirect.

    And I have done the redirect in the .htaccess file properly myself, and it works fine. It allows myself and any other dev IP needed.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mark

    (@markwolters)

    5 years, 2 months ago

    Hi @bernardberry646,

    if you have manually set an .htaccess redirect you can dismiss the Really Simple SSL notice by pressing the ‘dismiss’ link or the X next to it.

    Let me know if you have any other questions.

    Thread Starter bernardberry646

    (@bernardberry646)

    5 years, 2 months ago

    I am already aware of that, my point was moreso that the plugin (which works perfectly), notifies admin of an issue that technically, it shouldn’t. The redirect is in fact in my .htaccess already.

    So when it warns:
    WordPress 301 redirect enabled. We recommend to enable a 301 .htaccess redirect.
    It’s a bit misleading in my case, and maybe a few others who develop. Because, I thought for a minute, and was like, “WTH, didn’t I have this site locked down to just a few select IP’s already!?”

    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    5 years, 2 months ago

    @bernardberry646 what is the code of your .htaccess redirect? It checks for the most used .htaccess redirect code. Most variations are after that part, so should be pretty generic.

    If you can post your redirect code, I can compare, and maybe check for that one as well.

    Thread Starter bernardberry646

    (@bernardberry646)

    5 years, 2 months ago

    <Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>

#MAINTENANCE
Options -MultiViews +FollowSymLinks
RewriteEngine On

# Allow MainWP at M4M
RewriteCond %{REMOTE_ADDR} !XXX.XX.XX.XXX [NC]
RewriteCond %{REMOTE_ADDR} !XXX.XX.XX.XXX[NC]
RewriteCond %{REMOTE_ADDR} !XXX.XX.XX.XXX [NC]  

# Allow Devs
RewriteCond %{REMOTE_ADDR} !XXX.XX.XX.XXX [NC] #Dev_Name
RewriteCond %{REMOTE_ADDR} !XXX.XX.XX.XXX [NC]  #Dev_Name

# Allow real files to be served
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule .* http://temp_site_url [R=302,L]
    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    5 years, 2 months ago

    Hi @bernardberry646,

    I don’t see any https redirect in here. Unless I’m missing something, it looks like the notice in Really Simple SSL is correct.

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

The topic ‘301 redirect’ is closed to new replies.