Weird issue with double-slashes AFTER updating to 1.9.0

  • Resolved yallaman

    (@yallaman)


    1 year, 10 months ago

    After recently updating to version 1.9.0 (from a much earlier version) I have discovered something strange that I have never seen before. I’ve used WP Super Cache (great plugin!) for almost three years, and this is the only plugin I use on my speedy and very light-weight WP installation (currently running 6.0.2).

    In AWStats in cPanel I can see that my site gets thousands of hits/downloads on preload_permalink.txt at this URL:

    /wp/wp-content/cache//preload_permalink.txt

    This has never occurred before. Please also note the double slash (//) before the file name!

    preload_permalink.txt always contains only a single line with the number 275 followed by the URL of one the pages on my website (below, I have substituted my URL with an example):

    275 https://www.example.com/page/

    I have not made any other changes to my site lately. I have tried deleting all the cache and running preload again, but I keep getting lots of hits on /wp/wp-content/cache//preload_permalink.txt. The file always contains the same line (see above).

    Caching seems to work fine, though, including the above-mentioned URL/page. By inspecting the page source in my browser, I can see that it’s loading the preloaded/cached version, just like it did prior to updating the plugin.

    The changelog for version 1.9.0 says “Fixes to URL parsing to prevent cache pollution issues around URLs with double-slashes. [#26247]”.

    I never had any issues with double-slashes prior to updating, but it seems I do now… It doesn’t make sense to me.
    AWStats have also started reporting “508 Loop Detected (WebDAV)” status code, which has never happened in the 14 years I’ve had this website. I’m not sure if this could be related to the double-slash issue.

    Any idea what’s going on?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Mike Stott

    (@mikemayhem3030)

    1 year, 10 months ago

    Hi @yallaman

    When you run the preloader do you leave the tab open and watch the progress?

    When you’ve run the preloader previously (before 1.9.0) did you keep the tab open then too?

    Thanks for highlighting the double slash too, we’ll take a look into why that is.

    Thread Starter yallaman

    (@yallaman)

    1 year, 10 months ago

    Thanks for your reply, @mikemayhem3030.

    Yes, after hitting the “Preload Cache Now” button, I wait until the preload process has finished before I do anything else in WordPress (it takes about 15 minutes). However, there is nothing to watch when doing this…

    I have always done it this way, both before and after 1.9.0, because I don’t know if the process will continue “in the background” if I move away from the “Preload” tab. I use FileZilla (FTP client) to check when the preload process is done.

    • This reply was modified 1 year, 10 months ago by yallaman.
    Plugin Contributor Mike Stott

    (@mikemayhem3030)

    1 year, 10 months ago

    @yallaman I’m pretty sure the hits/downloads on that page reported by AWS are due to the preloader process and nothing to worry about.

    If it becomes and issue just open a new reply here, in the meantime I’ve logged the // issue and will mark this as resolved.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Weird issue with double-slashes AFTER updating to 1.9.0’ is closed to new replies.

Tags