Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pawkat

    Thank you for reaching out and I am happy to answer.
    The reason this happens is that page enhanced rules work with and without trailing slash. We don’t know if the user wants the trailing slash or not. Also adding a rewrite rule in the Nginx or Apache config, we can’t do that because we don’t know which URLs should be opposite. For example, the contact form 7 plugin doesn’t work with a trailing slash, but we don’t know if the user installed that plugin. Also, we don’t know what plugins work with what rules and we don’t want to have to add a million possibilities for each plugin there is.

    I hope this answers your question.`
    Thanks!

    Thread Starter pawkat

    (@pawkat)

    Hello @vmarko, thankyou for your answer.
    Can you please tell me what will change if I change the caching method to the Disk: Basic? And can I somehow fix this without changing the caching method?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pawkat

    As I’ve mentioned in my previous post, there is nothing that can be done when using Disk: Enhanced
    Disk Basic – invokes a PHP script, similar to the standard wp-cache plugin.
    Enhanced – avoids invoking any PHP script, It serves cached pages using the server’s URL rewriting capabilities, skipping PHP and WordPress entirely. It’s faster and more efficient.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘trailing slash redirect doesn’t work’ is closed to new replies.