Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <5419BC66.3030103@rcbowen.com>
Date: Wed, 17 Sep 2014 12:52:54 -0400
From: Rich Bowen <rbowen@rcbowen.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: users@httpd.apache.org
References: <54188662.9080502@tribloom.com>
In-Reply-To: <54188662.9080502@tribloom.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] (36)File name too long


On 09/16/2014 02:50 PM, mmccarthy@tribloom.com wrote:
> I am using RewriteRule and the proxy flag to proxy through Apache. 
> When a long URL is passed through (longer than 255 characters), I get 
> the error below (redacted). I understand that this is related to the 
> maximum file name on the OS, in this case Ubuntu 14.04. My question is 
> why is this happening when the URL is not related to a file on the 
> file system? The URL is rewritten, then proxied to another server that 
> works fine with long URLs.
>
> [Mon Sep 15 11:42:04.211290 2014] [core:error] [pid 18302:tid 
> 140171735451392] (36)File name too long: [client xxx.xx.x.xxx:53717] 
> AH00036: access to /<long file path>/_aliases failed (filesystem path 
> '/<long file path>), referer: http://xx.xx.xx.xxx/index.html
>
> Thanks,

That error message doesn't appear to be from the httpd server itself 
(ie, that message doesn't appear anywhere in the source code for trunk, 
2.4, 2.2, or 2.0), which leads me to believe that 1) it's in fact from 
your filesystem, and 2) there's no direct way to fix that in httpd 
configuration.

As thy why it matters when the file isn't on the filesystem, that's hard 
to tell without more context, but I presume that at some point in the 
process it is *looking* for the file in the filesystem.

For example, if this RewriteRule is in a .htaccess file, rather than in 
the main server config, it did in fact have to navigate to a filesystem 
directory before consulting that .htaccess file.

-- 
Rich Bowen - rbowen@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org