RewriteRule .* – [E=HTTP_MOD_REWRITE:On]

  • Resolved oanhtran1804

    (@oanhtran1804)


    8 years, 7 months ago

    Hi after install the plugin i got warning, part of my web is not secure SSL. It not happen before, which i’m paid user SSL and use really simple SSL to force all source code load HTTPs correct.

    SO
    1) RewriteRule .* – [E=HTTP_MOD_REWRITE:On]
    Can i change HTTP to HTTPS, final i have
    RewriteRule .* – [E=HTTPS_MOD_REWRITE:On]

    2) #WriteCheckString:1508754878_53712
    What is meaning of this note? I saw it difference everytime i delete/ re-install

    3) What is it mean of
    [L]
    [L,QSA]
    [NC]

    4)
    It seem too much redirect throw out 404 in .htaccess, which is not good for check up speed of website
    How do i make it throw out custom url status 301 for better speed up website?

    5) What is the usefull of cookie in .htaccess?
    RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in.*$ [NC]

    Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Maya

    (@tdgu)

    8 years, 7 months ago

    Hi,
    I would try to explain, but the responses would be too technical. I think the best will be to check with the actual plugin code. Also see Apache / IIS rewrite specifications.

    Here’s some fast guides:

    1) Nope, it does not have to do with SSL at all, it’s just an environment variable.
    2) This is a checksum to ensure write where successfully.
    3) This is a large area to cover in words see http://httpd.apache.org/docs/current/mod/mod_rewrite.html
    4) Not all all, they are not redirect but internal WordPress 404. Those are triggering for unwanted slugs e.g. changed wp-admin
    5) See http://httpd.apache.org/docs/current/mod/mod_rewrite.html This line in particular check if user is logged-in.

    Thanks

    Thread Starter oanhtran1804

    (@oanhtran1804)

    8 years, 7 months ago

    Thank you so much for explain, i got understand.

    I found bellow usefull function, can you share me these code to use in my wordpress blog:
    1) Remove profile link meta tag within head.
    2) Remove all HTML new line carriage which makes all tags to appear on a single line.
    ===
    3) After setting your plugin complete, i got blocked out, used correct username+pass, but it never let me login, always tell me wrong pass. What is wrong? To cover i must delete active plugin direct in cpanel. and login as the same pass as normal. If i active, i get same issue.

    4) You given http://example.com?wph-recovery=1b48ab7ae839aed3ae1ba8badbf8bb8d
    What is uesfull or anyone know this, will allow login my admin as fake recover if they know my admin account and hacked pass?

    Thanks

    Plugin Contributor Maya

    (@tdgu)

    8 years, 7 months ago

    1) This is supported by plugin, see the options.
    2) This is supported by plugin, see the options.
    3) You need to clear the browser cache and even restart-it to be able to use the new cookie instead the cached data.
    4) Through that link you can reset all plugin setting and reverse back as before.

    Thanks

    Thread Starter oanhtran1804

    (@oanhtran1804)

    8 years, 7 months ago

    1+2 i know, can you share me this custom code, so i can create post for my blog.
    3. Is every web have there own =1b48ab7ae839aed3ae1ba8badbf8bb8d, or any web have same recover url? Sorry my hosting plan can not create sub domain for test.

    Plugin Contributor Maya

    (@tdgu)

    8 years, 7 months ago

    Well, the recovery code is unique for each site.

    Thread Starter oanhtran1804

    (@oanhtran1804)

    8 years, 7 months ago

    ok thanks for your respond.

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

The topic ‘RewriteRule .* – [E=HTTP_MOD_REWRITE:On]’ is closed to new replies.