Thanks for advice, but no luck here. I've tried the both variants (mod_proxy before and mod_proxy after mod_rewrite), but nothing changed. Axel-Stéphane SMORGRAV wrote: > No reason to get cranky there. > > My first thought also was that you are missing a proxy module. I understand you are using Apache 1.3. What about the order in which the modules are loaded? Could you try to rearrange them by putting the AddModule statement either at the top or the bottom of the list of modules, or at least before or after the rewrite module ? > > If memory serves me right, the modules added last are the ones executed first. You want mod_proxy to be executed after mod_rewrite so mod_rewrite must be loaded after mod_proxy. > > -ascs > > -----Original Message----- > From: news [mailto:news@xxxxxxxxxxxxx] On Behalf Of Alexander Prohorenko > Sent: Monday, August 29, 2005 7:41 AM > To: users@xxxxxxxxxxxxxxxx > Subject: [users@httpd] Re: Problems with proxying remote URLs > > Joshua Slive wrote: > >>On 8/28/05, Alexander Prohorenko <alexander.prohorenko@xxxxxxxxx> wrote: > > >>>I've got problem with using a mod_rewrite module using [P] keyword to >>>proxy a request. Everything works just fine with local files and >>>redirects, but when I'm trying to use a redirect with proxy to remote >>>destination I'm getting something like: >>> >>>[Sun Aug 28 14:05:36 2005] [error] [client 1.2.1.2] File does not exist: >>>proxy:http://my.domain.com/zzz >> >> >>Check that you have mod_proxy loaded statically (httpd -l) or >>dynamically (via LoadModule). > > > Of course it's loaded. > > white@artiste:/usr/local/etc/apache>grep proxy httpd.conf > > LoadModule proxy_module libexec/apache/libproxy.so > AddModule mod_proxy.c > > If it'd not be loaded, how would the usual proxying of local files work? > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|