Carsten Wiedmann schrieb:
> It's the same as with:
> | RewriteRule ^.*$ - [R=400]
>
> BTW:
> If "httpd-multilang-errordoc.conf" is enabled, all above solutions are also
> not working nice. Because now the error document shows:
Just for the records. This is doing the trick:
| NameVirtualHost *:80
William A. Rowe Jr. schrieb:
>> Well, and the error document with [R=400] (or other status codes) is also
>> not multi language.
>
> Right; presume for a moment that anyone hitting your server with a bogus dns
> reference or by-ip is doing so in a less-than-friendly, spidery or malicious
> manner.
Carsten Wiedmann wrote:
>
> Well, and the error document with [R=400] (or other status codes) is also
> not multi language.
Right; presume for a moment that anyone hitting your server with a bogus dns
reference or by-ip is doing so in a less-than-friendly, spidery or malicious
manner. Are they r
William A. Rowe Jr. schrieb:
> RewriteRule .* - [R=400]
Hm, ok, I've never realized, that I can set other status codes in
RewriteRule [R], then the well known redirect status codes (Redirection
3xx). A little bit curious?
With [R=400] it's the same as with the Perl script (thanks for this hin
Carsten Wiedmann wrote:
> William A. Rowe Jr. schrieb:
>> I agree it should be easier, Rich and I have it down to 3-4 lines of rewrite
>> magic
>> to kick out a 400, but we should probably allow this to be explicit
>> [default?]
>
> That would be nice. And if I'm be able to set the status code i
William A. Rowe Jr. schrieb:
> I agree it should be easier, Rich and I have it down to 3-4 lines of rewrite
> magic
> to kick out a 400, but we should probably allow this to be explicit [default?]
That would be nice. And if I'm be able to set the status code in a
RewriteRule and/or Header directi
André Warnier schrieb:
> But is is interesting to see how in the end, a document such as RFC2616
> which is meant to "specify" a relatively strict set of rules, and of
> which I am sure the phrasing is examined carefully and repeatedly (it
> being after all a revision of an earlier document on the
Eric Covener wrote:
On Sat, Nov 28, 2009 at 7:23 PM, Carsten Wiedmann wrote:
André Warnier schrieb:
So how do you enumerate invalid hosts explicitly then ?
Right, it's a little bit curious, that you can't set 400 with mod_rewrite
(or header), only 403 (or 410).
In 2.2.x you can probably use
On Sat, Nov 28, 2009 at 7:23 PM, Carsten Wiedmann wrote:
> André Warnier schrieb:
>> So how do you enumerate invalid hosts explicitly then ?
>
> Right, it's a little bit curious, that you can't set 400 with mod_rewrite
> (or header), only 403 (or 410).
In 2.2.x you can probably use [R=400]
--
André Warnier schrieb:
> So how do you enumerate invalid hosts explicitly then ?
Right, it's a little bit curious, that you can't set 400 with mod_rewrite
(or header), only 403 (or 410).
That's what I'm always doing:
httpd-vhosts.conf:
| NameVirtualHost *:80
|
|
| ServerName nohost
| R
10 matches
Mail list logo
