PHWinfo - Afficher un message

13/10/2006, 20h55

On Oct 13, 3:20 pm, Bob Arn <nom...@nomail.bob> wrote:
> Is there a way to redirect on "file name too long" errors?
>
> I'm using mod_rewrite to handle all unknown urls with an error page.
> That's not working for this error. Apparently the "file name too long"
> error occurs before mod_rewrite is invoked.
>
> Setting up an ErrorDocument is also ignored, even though it looks to the
> user (and listed in access.log) as a 403 error, it's not a normal 403
> error.

What is the exact error message? I don't know of any "file name too
long" error. Perhaps you are thinking of the error that occurs when
the URI is bigger than the configured limit:
http://httpd.apache.org/docs/2.2/mod...mitrequestline

In general, these types of errors will not use ErrorDocuments supplied
by the admin. This is because the limits are made in the first place
to prevent resource usage or other bugs that may be triggered by
very-large inputs from the client. If you allow those requests to pass
through the normal request-processing phases (in order to trigger the
ErrorDocument) you expose the server to the very-large inputs. So
instead, they are simply immediately rejected with a hard-coded
message.

If you know your server can handle it, you can simply increase
LimitRequestLine to a very-large value.

Joshua.

13/10/2006, 20h55	#2
Joshua Slive Messages: n/a Hébergeur:	Re: Catching "File name too long" errors On Oct 13, 3:20 pm, Bob Arn <nom...@nomail.bob> wrote: > Is there a way to redirect on "file name too long" errors? > > I'm using mod_rewrite to handle all unknown urls with an error page. > That's not working for this error. Apparently the "file name too long" > error occurs before mod_rewrite is invoked. > > Setting up an ErrorDocument is also ignored, even though it looks to the > user (and listed in access.log) as a 403 error, it's not a normal 403 > error. What is the exact error message? I don't know of any "file name too long" error. Perhaps you are thinking of the error that occurs when the URI is bigger than the configured limit: http://httpd.apache.org/docs/2.2/mod...mitrequestline In general, these types of errors will not use ErrorDocuments supplied by the admin. This is because the limits are made in the first place to prevent resource usage or other bugs that may be triggered by very-large inputs from the client. If you allow those requests to pass through the normal request-processing phases (in order to trigger the ErrorDocument) you expose the server to the very-large inputs. So instead, they are simply immediately rejected with a hard-coded message. If you know your server can handle it, you can simply increase LimitRequestLine to a very-large value. Joshua.