Support » Plugin: W3 Total Cache » [Plugin: W3 Total Cache] Page Caching produces .htaccess file that is too long

  • Resolved Brian Layman

    (@brianlayman)


    When I go to turn on page caching the line from .htaccess that starts “RewriteCond %{REQUEST_URI}” ends up being 101,544 characters long.

    I’m working with a rather large site. I’m wondering if it wouldn’t be better to somehow build that line as a ! condition and find the standard urls to exclude.

    Do you think that’s an avenue worth investigating? Do you see another alternative?

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Frederick Townes

    (@fredericktownes)

    You mean the line is so long that it causes 500 errors or something?

    Thanks for replying Frederick.

    Yes, that’s exactly what was happening.

    In the end I simply used output buffering in index.php. An if statement to check to see if the user is logged in or not and the whole thing is blazingly fast under extreme load.

    Plugin Author Frederick Townes

    (@fredericktownes)

    Thanks for the input.

    Plugin Author Frederick Townes

    (@fredericktownes)

    I suppose you have extremely long list of “Accept/Reject URIs” in w3tc config? Note you dont have to specify each URL – regular expressions are allowed there. Having long list of files there will cause significant performance problems in any case.

    Brian Layman

    (@brianlayman)

    I’m not involved with the client any longer, but I simply had activated the plugin activated page cache and told it it could modify the .htaccess file. After that I got a 500 error.

    The site was a very large mu install (212K blogs) site with a very large number of articles on the primary blog on which I was activating w3tc.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: W3 Total Cache] Page Caching produces .htaccess file that is too long’ is closed to new replies.