What is source of this server error?

The following error is repeating itself on my server:

[Mon Sep 17 11:16:58 2012] [warn] RewriteCond: NoCase option for non-regex pattern ‘-f’ is not supported and will be ignored.

Any idea what is causing this error? Or how I can track it down?

Thanks,

Ed

  • aecnu
    • WP Unicorn

    Greetings Ed,

    Thank you for this great question and a significant item to bring up.

    It appears to me that this is an htaccess issue or permalinks.

    Could you please first reset your permalinks and if still getting the error please post the contents of your htaccess file here.

    Please advise.

    Cheers, Joe

  • exberry
    • The Incredible Code Injector

    Hi Joe,

    Thanks for your help. I reset the permalinks for all my 9 multisites by saving the permalinks. This has not stopped the error from occuring.

    Below is a copy of my htaccess file.

    Ed

    RewriteEngine on

    RewriteCond %{HTTP_HOST} ^climatephysics.org$ [OR]

    RewriteCond %{HTTP_HOST} ^www.climatephysics.org$

    RewriteRule ^/?$ “http://climatephysics.com/” [R=301,L]

    # Use PHP5 Single php.ini as default

    AddHandler application/x-httpd-php5s .php

    # BEGIN W3TC Browser Cache

    <IfModule mod_deflate.c>

    <IfModule mod_setenvif.c>

    BrowserMatch ^Mozilla/4 gzip-only-text/html

    BrowserMatch ^Mozilla/4.0[678] no-gzip

    BrowserMatch bMSIE !no-gzip !gzip-only-text/html

    BrowserMatch bMSI[E] !no-gzip !gzip-only-text/html

    </IfModule>

    <IfModule mod_headers.c>

    Header append Vary User-Agent env=!dont-vary

    </IfModule>

    <IfModule mod_filter.c>

    AddOutputFilterByType DEFLATE text/css application/x-javascript text/x-component text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon

    </IfModule>

    </IfModule>

    <FilesMatch “.(css|js|htc|CSS|JS|HTC)$”>

    FileETag None

    <IfModule mod_headers.c>

    Header set X-Powered-By “W3 Total Cache/0.9.2.4”

    </IfModule>

    </FilesMatch>

    <FilesMatch “.(html|htm|rtf|rtx|svg|svgz|txt|xsd|xsl|xml|HTML|HTM|RTF|RTX|SVG|SVGZ|TXT|XSD|XSL|XML)$”>

    FileETag None

    <IfModule mod_headers.c>

    Header set X-Powered-By “W3 Total Cache/0.9.2.4”

    </IfModule>

    </FilesMatch>

    <FilesMatch “.(asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|gif|gz|gzip|ico|jpg|jpeg|jpe|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|mpg|mpe|mpp|otf|odb|odc|odf|odg|odp|ods|odt|ogg|pdf|png|pot|pps|ppt|pptx|ra|ram|svg|svgz|swf|tar|tif|tiff|ttf|ttc|wav|wma|wri|xla|xls|xlsx|xlt|xlw|zip|ASF|ASX|WAX|WMV|WMX|AVI|BMP|CLASS|DIVX|DOC|DOCX|EOT|EXE|GIF|GZ|GZIP|ICO|JPG|JPEG|JPE|MDB|MID|MIDI|MOV|QT|MP3|M4A|MP4|M4V|MPEG|MPG|MPE|MPP|OTF|ODB|ODC|ODF|ODG|ODP|ODS|ODT|OGG|PDF|PNG|POT|PPS|PPT|PPTX|RA|RAM|SVG|SVGZ|SWF|TAR|TIF|TIFF|TTF|TTC|WAV|WMA|WRI|XLA|XLS|XLSX|XLT|XLW|ZIP)$”>

    FileETag None

    <IfModule mod_headers.c>

    Header set X-Powered-By “W3 Total Cache/0.9.2.4”

    </IfModule>

    </FilesMatch>

    # END W3TC Browser Cache

    # BEGIN WordPress

    RewriteBase /

    RewriteRule ^index.php$ – [L]

    # uploaded files

    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

    # add a trailing slash to /wp-admin

    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]

    RewriteCond %{REQUEST_FILENAME} -d

    RewriteRule ^ – [L]

    RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]

    RewriteRule ^[_0-9a-zA-Z-]+/(.*.php)$ $1 [L]

    RewriteRule . index.php [L]

    # END WordPress

    <Files 403.shtml>

    order allow,deny

    allow from all

    </Files>

  • exberry
    • The Incredible Code Injector

    Thank you, maxaud,

    Yes, I still get the error after making this edit.

    I also removed lines 2-4 with no change in the error:

    # RewriteCond %{HTTP_HOST} ^climatephysics.org$ [OR]

    # RewriteCond %{HTTP_HOST} ^www.climatephysics.org$

    # RewriteRule ^/?$ “http://climatephysics.com/” [R=301,L]

    Ed

  • aecnu
    • WP Unicorn

    Greetings Ed,

    Thank you for posting the htaccess file contents and the additional input, it is certainly appreciated.

    I see that you have the W3 Total Cache plugin running, and I will tell you upfront that I am not a fan of any of the caching schemes preferring real server power beef over what I consider BS. But of course that is my own experience and opinion with testing and checking out these caching items.

    If in fact you are running a MultiSite installation? A heads up that no where on W3’s page does it indicate it is MultiSite compatible.

    You may want to test it disabling it and see if you still get the error.

    For comparison purposes I have included a screen shot of my htaccess file from my test production server:

    <files wp-config.php>
    order allow,deny
    deny from all
    </files>

    # BEGIN WordPress
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index.php$ - [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule . index.php [L]
    # END WordPress

    Please advise.

    Cheers, Joe

  • exberry
    • The Incredible Code Injector

    Thank you very much, Joe.

    I removed W3 Total Cache and my site began running about ten times as fast without W3 than with it. Also, all the throttling disappeared.

    Then I deleted W3 which turned out to be an adventure in itself.

    Then I used your htaccess in place of mine shown above and my site works just fine. So we accomplished a lot.

    But for some reason, the same warning that I began this thread with, still goes on. Now, however, it is more of a curiousity than a problem since it does not appear to be hindering my site.

    Thanks very much, but I will still entertain more ideas on how to stop the warning messages.

    Ed

  • aecnu
    • WP Unicorn

    Greetings Ed,

    Yes sir uninstalling W3 can be a bear, that is for certain.

    But for some reason, the same warning that I began this thread with, still goes on.

    The warning in itself is not such a big item compared to failures and errors, but would indeed be great to figure out. I will see if our lead developer @aaron may have a possible clue for us on this one.

    He is extremely busy but we have made it so far I hate to give up now.

    Though this may take a bit longer then a normal ticket, I will try to get him in here asap.

    Cheers, Joe

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.