Forced Trailing Slash Removes After Cache Primed.

  • I was using WP Rocket as it was giving me very good results in speed.

    All URLs of my website need to have a forced trailing slash [/].

    I have fixed the problem in my .htaccess file too.

    Trailing Slash comes when I delete my cache. But when the cache is primed. Again the pages are loading without trailing slashes too.

    Example, 1. example.com/krishna/ [This is also loading.]
    2. example.com/krishna [This is also loading.]

    I want the 2nd one to be redirected to the first one. Everything seems okay in .htaccess, I’ve tried a lot of plugins to do this still failed.

    I am using Google Cloud Bitnami WordPress.

    Nothing works. You people are my last hope.
    Also, please explain me in simple language.

    Here is my.htaccess if you need.
    https://pastebin.com/zQHh7iTY

    PLEASE HELP MEE DEAR…

Viewing 1 replies (of 1 total)

  • I just set up a brand new WordPress sandbox site to test this out.

    I’ve not done ANY custom htaccess tweaks, I’m using the default Twenty Twenty One theme, and I have no plugin activated at all, and my permalink setting is /%postname%/

    Here’s a sample page (accessible within the next 24 hours only):

    https://s-qq2lmfw5mrn7.eu1.wpsandbox.org/hello-world

    If you visit this page, it seems WordPress is automatically enforcing the trailing slash, 301-redirecting the non-slash URL to the slash URL.

    Again, no custom htaccess rules involved (other than what WordPress automatically generates).

    I’m not very familiar with the WP Rocket plugin and how it serves cached content. And as this is a commercial plugin, it’s impossible for us to test anything and help you out — as WordPress support volunteers are not giving access to commercial products.

    I’ll advise you to contact the WP Rocket authors for their take on this.

Viewing 1 replies (of 1 total)
  • The topic ‘Forced Trailing Slash Removes After Cache Primed.’ is closed to new replies.