Re: [users@httpd] (36)File name too long

2014-09-17 Thread Rich Bowen
On 09/16/2014 02:50 PM, mmccar...@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

Re: [users@httpd] (36)File name too long

2014-09-17 Thread Jeff Trawick
On Wed, Sep 17, 2014 at 12:52 PM, Rich Bowen rbo...@rcbowen.com wrote: On 09/16/2014 02:50 PM, mmccar...@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

Re: [users@httpd] (36)File name too long

2014-09-17 Thread Jim Jagielski
It's from ap_directory_walk() else if ((rv != APR_SUCCESS rv != APR_INCOMPLETE) || !(thisinfo.valid APR_FINFO_TYPE)) { /* If we hit ENOTDIR, we must have over-optimized, deny * rather than assume not found. */

Re: [users@httpd] (36)File name too long

2014-09-17 Thread mmccar...@tribloom.com
Thanks for the info. I think the problem is that I am trying to use the REMOTE_USER in the rewrite for example: RewriteCond %{LA-U:REMOTE_USER} !^$ Which is later used in the RewriteRule. I just checked and found that when I remove the LA-U:REMOTE_USER part of the rewrite rule the error does

[users@httpd] (36)File name too long

2014-09-16 Thread mmccar...@tribloom.com
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