>
> Apache does not do reverse lookups on client host IPs by default.
> See:
> http://httpd.apache.org/docs/2.0/mod/core.html#hostnamelookups
>
Thanks'
Pedro
-
The official User-To-User support forum of the Apache HTTP Ser
On 1/12/07, Peter Huesser <[EMAIL PROTECTED]> wrote:
>
> Another thought: Did you set the directive RewritelogLevel at least to
> 4? (6 = highest used). Below loglevel 4, the processing of conditions
> is not being logged.
>
Wow, that was the break-through.Had a loglevel of 3 until now. Here the
>
> Another thought: Did you set the directive RewritelogLevel at least to
> 4? (6 = highest used). Below loglevel 4, the processing of conditions
> is not being logged.
>
Wow, that was the break-through.Had a loglevel of 3 until now. Here the
new log entries:
129.129.194.181 - - [12/Jan/2007:10:0
Peter Huesser wrote:
Bob wrote:
following entries in httpd.conf:
RewriteEngine On
RewriteCond %{REMOTE_HOST} \.domain\.ch$
RewriteRule ^/testtinfo/fea http://another.url.ch/
The produced entries in rewrite.log are:
129.129.194.181 - - [11/Jan/2007:09:40:24 +0100]
[server.psi.ch/sid#80c
>
> Is there a .htaccess file somehwere in your mailmain install? If so,
> have a look in there...
>
No.
Pedro
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslis
On 1/11/07, Peter Huesser <[EMAIL PROTECTED]> wrote:
> What might also be an issue here is that reverse DNS doesn't work
> properly.
>
> However, what you are trying to achieve might be better done
> differently. See another post in this forum. You ought to set up two
> virtual hosts, one on po
Bob wrote:
>> following entries in httpd.conf:
>>
>> RewriteEngine On
>> RewriteCond %{REMOTE_HOST} \.domain\.ch$
>> RewriteRule ^/testtinfo/fea http://another.url.ch/
>>
>> The produced entries in rewrite.log are:
>>
>> 129.129.194.181 - - [11/Jan/2007:09:40:24 +0100]
>> [server.psi.ch/sid#
Peter Huesser wrote:
following entries in httpd.conf:
RewriteEngine On
RewriteCond %{REMOTE_HOST} \.domain\.ch$
RewriteRule ^/testtinfo/fea http://another.url.ch/
The produced entries in rewrite.log are:
129.129.194.181 - - [11/Jan/2007:09:40:24 +0100]
[server.psi.ch/sid#80c1cc8][rid#814
> What might also be an issue here is that reverse DNS doesn't work
> properly.
>
> However, what you are trying to achieve might be better done
> differently. See another post in this forum. You ought to set up two
> virtual hosts, one on port 80 and one on port 443. Have a redirect to
> the htt
On 1/9/07, Bob <[EMAIL PROTECTED]> wrote:
Huesser Peter wrote:
> My interpretation of "RewriteCond
> %{REMOTE_HOST} \.domain\.ch$" is the following: If the client that makes
> the https request is within the "domain.ch" than apply the following
> RewriteRule.
Yes, this will cause a reverse DNS l
>
> Usually not in server context, mod_rewrite acts before the mapping to
> filesystem occurs. You said that the rewrite log is completely empty,
> when you request /testtinfo/fea? That would mean the rules are not
seen
> at all, e.g. a matched and the rules are defined in the
> main server confi
Huesser Peter wrote:
Yes, this will cause a reverse DNS lookup of remote_addr. But anyway,
I
think your order is incorrect. If your request comes through port 80,
the 2nd rule won't have any effect, because your first rule matched
already.
RewriteEngine On
RewriteCond %{REMOTE_HOST} \.domain\.
>
> Yes, this will cause a reverse DNS lookup of remote_addr. But anyway,
I
> think your order is incorrect. If your request comes through port 80,
> the 2nd rule won't have any effect, because your first rule matched
> already.
>
> RewriteEngine On
> RewriteCond %{REMOTE_HOST} \.domain\.ch$
> Re
Huesser Peter wrote:
My interpretation of "RewriteCond
%{REMOTE_HOST} \.domain\.ch$" is the following: If the client that makes
the https request is within the "domain.ch" than apply the following
RewriteRule.
Yes, this will cause a reverse DNS lookup of remote_addr. But anyway, I
think your o
>
> What are you seeing in your rewrite log? (If you don't have a rewrite
> log, switch it on now, and set debugging to a sufficiently high
> level).
>
Thanks for your answer. I turned it on and see nothing in the
rewrite.log file for the second RewriteCond (the first works fine and
produces seve
On 1/8/07, Huesser Peter <[EMAIL PROTECTED]> wrote:
I have a problem with a rewrite. In my httpd.conf I use the following lines:
ScriptAlias /test/ /var/test/cgi-bin/
Alias /pipermail/ /var/test/archives/public/
Options +FollowSymlinks
RewriteEngine On
RewriteCond %{SERVER_P
16 matches
Mail list logo
