You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modproxy-dev@apache.org by Tsai Li Ming <ma...@ltsai.com> on 2004/09/22 05:07:25 UTC
dns lookup for reverse proxy
Dear all,
I have the following directives in my conf file.
<ifmodule mod_proxy.c>
proxyrequests off
RewriteEngine On
ProxyPass /Server/ http://localhost:8081
ProxyPassReverse /Server/ http://localhost:8081
RewriteRule ^/Server$ /Server/ [P]
</IfModule>
My error log:
[Wed Sep 22 02:59:41 2004] [error] [client 192.168.1.22] proxy: DNS
lookup failure for: example2 returned by /Server
Does a force proxy requires a dns lookup on the httpd server itself?
When I change from a [P] to a [R], it works but our client does not
understand a http 302 (axis client).
-Liming
Re: dns lookup for reverse proxy
Posted by Ian Holsman <Ia...@cnet.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
try changing it to
> <ifmodule mod_proxy.c>
> ProxyPass /Server http://localhost:8081
> ProxyPassReverse /Server http://localhost:8081
> </ifmodule>
?
On 22/09/2004, at 1:33 PM, Tsai Li Ming wrote:
> It didn't work, because it's not under the DocumentRoot.
> [Wed Sep 22 03:30:14 2004] [error] [client 192.168.1.22] File does not
> exist: /var/www/html/Server
>
> -Liming
>
>
>
> Ian Holsman wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > try something like
> > <ifmodule mod_proxy.c>
> > ProxyPass /Server/ http://localhost:8081/
> > ProxyPassReverse /Server/ http://localhost:8081/
> > </ifmodule>
> >
> > you shouldn't need the other stuff to make it work
> >
> >
> > On 22/09/2004, at 1:07 PM, Tsai Li Ming wrote:
> >
> >> Dear all,
> >>
> >> I have the following directives in my conf file.
> >>
> >> <ifmodule mod_proxy.c>
> >> proxyrequests off
> >> RewriteEngine On
> >>
> >>
> >> ProxyPass /Server/ http://localhost:8081
> >> ProxyPassReverse /Server/ http://localhost:8081
> >> RewriteRule ^/Server$ /Server/ [P]
> >> </IfModule>
> >>
> >>
> >>
> >> My error log:
> >> [Wed Sep 22 02:59:41 2004] [error] [client 192.168.1.22] proxy: DNS
> >> lookup failure for: example2 returned by /Server
> >>
> >> Does a force proxy requires a dns lookup on the httpd server itself?
> >> When I change from a [P] to a [R], it works but our client does not
> >> understand a http 302 (axis client).
> >>
> >> -Liming
> >>
> > - --
> > Ian Holsman
> > Director
> > Network Management Systems
> > CNET Networks
> > PH: 415-344-2608 (USA) /(++61) 3-9818-0132 (Australia)
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (Darwin)
> >
> > iD8DBQFBUPElq3pgvCz4ZCcRAqP8AJ9bm2/Lvdqbg3Y+vEOIsXl+hvC/ngCfSM8e
> > HDDFrCA18WEQXIdwWWOj4AA=
> > =Qf5L
> > -----END PGP SIGNATURE-----
> >
> >
>
- --
Ian Holsman
Director
Network Management Systems
CNET Networks
PH: 415-344-2608 (USA) /(++61) 3-9818-0132 (Australia)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBUSTAq3pgvCz4ZCcRAuPgAJ9OtdmqHApve9GJwlMUIl5QVqXNNgCcDLJP
nZtE6/iDQydbQVDdkUXN+wQ=
=evaX
-----END PGP SIGNATURE-----
Re: dns lookup for reverse proxy
Posted by Tsai Li Ming <ma...@ltsai.com>.
It didn't work, because it's not under the DocumentRoot.
[Wed Sep 22 03:30:14 2004] [error] [client 192.168.1.22] File does not
exist: /var/www/html/Server
-Liming
Ian Holsman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> try something like
> <ifmodule mod_proxy.c>
> ProxyPass /Server/ http://localhost:8081/
> ProxyPassReverse /Server/ http://localhost:8081/
> </ifmodule>
>
> you shouldn't need the other stuff to make it work
>
>
> On 22/09/2004, at 1:07 PM, Tsai Li Ming wrote:
>
>> Dear all,
>>
>> I have the following directives in my conf file.
>>
>> <ifmodule mod_proxy.c>
>> proxyrequests off
>> RewriteEngine On
>>
>>
>> ProxyPass /Server/ http://localhost:8081
>> ProxyPassReverse /Server/ http://localhost:8081
>> RewriteRule ^/Server$ /Server/ [P]
>> </IfModule>
>>
>>
>>
>> My error log:
>> [Wed Sep 22 02:59:41 2004] [error] [client 192.168.1.22] proxy: DNS
>> lookup failure for: example2 returned by /Server
>>
>> Does a force proxy requires a dns lookup on the httpd server itself?
>> When I change from a [P] to a [R], it works but our client does not
>> understand a http 302 (axis client).
>>
>> -Liming
>>
> - --
> Ian Holsman
> Director
> Network Management Systems
> CNET Networks
> PH: 415-344-2608 (USA) /(++61) 3-9818-0132 (Australia)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
>
> iD8DBQFBUPElq3pgvCz4ZCcRAqP8AJ9bm2/Lvdqbg3Y+vEOIsXl+hvC/ngCfSM8e
> HDDFrCA18WEQXIdwWWOj4AA=
> =Qf5L
> -----END PGP SIGNATURE-----
>
>
Re: dns lookup for reverse proxy
Posted by Ian Holsman <Ia...@cnet.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
try something like
<ifmodule mod_proxy.c>
ProxyPass /Server/ http://localhost:8081/
ProxyPassReverse /Server/ http://localhost:8081/
</ifmodule>
you shouldn't need the other stuff to make it work
On 22/09/2004, at 1:07 PM, Tsai Li Ming wrote:
> Dear all,
>
> I have the following directives in my conf file.
>
> <ifmodule mod_proxy.c>
> proxyrequests off
> RewriteEngine On
>
>
> ProxyPass /Server/ http://localhost:8081
> ProxyPassReverse /Server/ http://localhost:8081
> RewriteRule ^/Server$ /Server/ [P]
> </IfModule>
>
>
>
> My error log:
> [Wed Sep 22 02:59:41 2004] [error] [client 192.168.1.22] proxy: DNS
> lookup failure for: example2 returned by /Server
>
> Does a force proxy requires a dns lookup on the httpd server itself?
> When I change from a [P] to a [R], it works but our client does not
> understand a http 302 (axis client).
>
> -Liming
>
- --
Ian Holsman
Director
Network Management Systems
CNET Networks
PH: 415-344-2608 (USA) /(++61) 3-9818-0132 (Australia)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBUPElq3pgvCz4ZCcRAqP8AJ9bm2/Lvdqbg3Y+vEOIsXl+hvC/ngCfSM8e
HDDFrCA18WEQXIdwWWOj4AA=
=Qf5L
-----END PGP SIGNATURE-----