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
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.
*/
On Wed, Sep 17, 2014 at 12:52 PM, Rich Bowen 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 understan
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 th
On Wed, Sep 17, 2014 at 11:05 AM, Bill Vance wrote:
>
> Just a quick word of thanks to everyone who chimed in.
> John's decided to do a bit of boning up before taking
> the big plunge, so I guess I'm off the hook for now.
>
Good to hear!
FYI, I used to work in a company that wrote the
Just a quick word of thanks to everyone who chimed in.
John's decided to do a bit of boning up before taking
the big plunge, so I guess I'm off the hook for now.
:-)
Bill
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apa
Okay, thanks. It isn’t that important for me to get the SSILegacyExprParser off
if it’s already on in my configuration. I don’t have access to WHM.
But if the SSILegacyExprParser is on for me, why won’t this work?:
Shouldn’t it, if the legacy syntax is on?
/Simen
Fra: Yehuda Katz
Send
