My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 9: rfc - generated cache names are too long
4 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Closed:  Nov 2010

Sign in to add a comment
Reported by dogmatic69, Nov 3, 2010
What steps will reproduce the problem?
1. create a whole lot of css files
2. include them in a page
3. refresh so that the cache is generated

What is the expected output? What do you see instead?
a file name that the server can render. something like a hash and link the hash internally to that long string possibly 

error log:
[Thu Nov 04 01:29:33 2010] [error] [client] (36)File name too long: access to /cc.8d06446468a1b74b8b379d1462beb5a8.assets,_css,_960gs,_960,s+assets,_css,_admin_nav,s+assets,_css,_960gs,_uncompressed,_demo,s+assets,_css,_jquery_ui,s+projects,_css,_projects,s+gallery,_css,_gallery,s+gallery,_css,_style_1,s+thickbox,_css,_thickbox,s+contact,_css,_contact,s+comments,_css,_comment,s+filter,_css,_filter,s+tags,_css,_tags,s+debug_kit,_css,_debug_toolbar,s.css failed, referer:

What version of the product are you using? On what operating system?
mod_pagespeed 64-bit .deb ubuntu 10.10 x64 + 5.3.3-1ubuntu9.1 + Apache/2.2.16 (Ubuntu)

Please provide any additional information below.
long file names generate a 403 Forbidden for anyone else that gets this
Nov 3, 2010
Project Member #1
Thanks for the report.  As a workaround, you can disable 'combine_css' with:

kModPagespeedDisableFilters combine_css

in pagespeed.conf.  But I am curious what software is complaining about this particular case.   The URL in the issue report is about 423 characters long.  This is too long for a single-leaf filename, but mod_pagespeed does not need to use the URL as a filename.

Does anyone know what module would be printing this format of error message?

[Thu Nov 04 01:29:33 2010] [error] [client] (36)File name too long: access to ....

I just tried to search for "File name too long: access to " and I saw this error reported multiple times over the last few years, including:

I wonder if there's a simple patch to a mod_*.c file somewhere that could bump up a buffer size  to a higher limit. 

Nov 4, 2010
#2 dogmatic69
here are all the modules that are enabled on my install

[public_html dev ↑⚡] $ apache2 -l
Compiled in modules:
[public_html dev ↑⚡] $ ls /etc/apache2/mods-enabled/
alias.conf            autoindex.load  negotiation.conf  reqtimeout.load
alias.load            cgi.load        negotiation.load  rewrite.load
auth_basic.load       deflate.conf    pagespeed.conf    setenvif.conf
authn_file.load       deflate.load    pagespeed.load    setenvif.load
authz_default.load    dir.conf        php5.conf         status.conf
authz_groupfile.load  dir.load        php5.load         status.load
authz_host.load       env.load        proxy.conf
authz_user.load       mime.conf       proxy.load
autoindex.conf        mime.load       reqtimeout.conf

Its pretty much the default php5 install from apt-get install php5, i found some sites last night with this error being reported to apache

Nov 4, 2010
Same error here.

*What version of the product are you using? On what operating system?*
mod_pagespeed 32-bit .deb, Ubuntu/10.04 x32 + PHP/5.3.2-1ubuntu4.5 + Apache/2.2.14-5ubuntu8.3

Nov 5, 2010
Project Member #4
(No comment was entered for this change.)
Nov 5, 2010
I'm also experiencing this issue. Long URLs generated by the combine CSS filter are returning 403 forbidden
Nov 5, 2010
Project Member #6
I found the source of the problem in the httpd source.

I believe httpd is applying posix pathname limitations to URLs.  This is unfortunate as URLs can be much longer; there's no need for them to be limited by the file system.

But the only filter that's likely to be affected is combine_css and we'll put a ceiling on the pathnames that it generates to avoid this problem.

Nov 5, 2010
#7 dogmatic69
the reason it does that is because it first looks to see if there is a file of that name for some reason. This has been filed as a bug many times at apache and they will not fix it (going back 3 years or so) 

Nov 8, 2010
Project Member #8
(No comment was entered for this change.)
Summary: rfc - generated cache names are too long
Nov 11, 2010
Project Member #9
This has been fixed in the trunk, but the fix is not available in a binary release yet.

SVN trunk revision 180 has this change:

Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting