Caching URLs without trailing slash (Nginx)

  • Resolved JayMcTee

    (@jaymctee)


    10 years, 11 months ago

    Hi,

    Just enabled Falcon on a few sites, been using WordFence for a long time already.

    On most sites, I take off the trailing slash in URLs, for debatable SEO reasons. I noticed in the Nginx conf that you have:

    #Only cache URL's ending in /
        if ($request_uri !~ \/$) {
            set $wordfenceCacheOn 0;
        }

    Naturally, in my case, I don’t want that. But when I comment this out, only my homepage gets cached. I suppose somewhere in your code you have a similar check.

    How can I reliably enable caching of URLs ending with a character that isn’t a forward slash?

    What was your rationale to begin with, to only cash those ending in /? I don’t see the logic in this.

    Regards,

    Jay

    https://wordpress.org/plugins/wordfence/

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

    (@wfsupport)

    10 years, 11 months ago

    Hi

    I’ve sent this over to the dev team to get a proper answer for you. It might be Monday before that happens but I will let you know when I do.

    tim

    Thread Starter JayMcTee

    (@jaymctee)

    10 years, 11 months ago

    Hi Tim,

    Did you get a response from them?

    Similarly, on some sites we make post-name.html URLs for example, those two would fail your reg-exp checking for a trailing slash it seems.

    Would be great to make this more inclusive, allowing for a bigger variety of URLs.

    Regards,

    Jay

    Plugin Author Mark Maunder

    (@mmaunder)

    10 years, 11 months ago

    Hi Jay,

    We made this design choice because most WordPress sites with permalinks are structured in a way where anything that doesn’t end in a slash should probably not be cached e.g. .php scripts.

    I’m going to file a bug to consider providing an option to cache pages that don’t end in a slash.

    Regards,

    Mark.

    Thread Starter JayMcTee

    (@jaymctee)

    10 years, 11 months ago

    Thanks Mark,

    Appreciate you guys looking in to this, even if my use case doesn’t fit the standard model.

    Having said that, it is quite a big assumption that anything without a trailing / probably doesn’t need caching. Would be great if you gave us an option in admin instead of assuming.

    Having researched the latest on this, also from authorities like Yoast & Matt Cutts, it seems like leaving the trailing slash on just like WordPress defaults to is absolutely fine. Their own blogs have the trailing slash after all…

    MB Creation

    (@mbcreation)

    10 years, 6 months ago

    Hi, any update on this ?
    Seems to be the case on Apache too ?

    Thanks for your time and plugin.

    Plugin Author WFMattR

    (@wfmattr)

    10 years, 6 months ago

    This request is still in our queue, with reference number FB580. I don’t have an estimate of when it may be implemented yet, if it will be, due to the volume of requests we get, but it will still be evaluated. I’ve added your post to our system as well. Thanks for your interest!

    -Matt R

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

The topic ‘Caching URLs without trailing slash (Nginx)’ is closed to new replies.