httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunter Verbocht" <gun...@verbocht.be>
Subject RE: [users@httpd] Rewrite but keep original URL in browser
Date Thu, 23 Jan 2003 15:57:36 GMT
Hi,

You mentioned that only ProxyPass is replaced with [P]
How can I also replace the ProxyPassReverse? So if I want to use:

>>RewriteCond %{HTTP_HOST} ^(.+).domain.com$ [NC]
>>RewriteRule .* http://other.domain.com/user/$1 [P]

Regards,

Gunter Verbocht

-----Original Message-----
From: Boyle Owen [mailto:Owen.Boyle@swx.com] 
Sent: donderdag 23 januari 2003 13:04
To: users@httpd.apache.org
Subject: RE: [users@httpd] Rewrite but keep original URL in browser

>-----Original Message-----
>From: Gunter Verbocht [mailto:gunter@verbocht.be]
>
>I just wanted to thank you people. I have been successful with the
>following command to proxy from one server to the other one:
>>>ProxyPass		/  http://other.domain.com/userlogin/
>>>ProxyPassReverse	/  http://other.domain.com/userlogin/

This is the simplest solution. If this works - go for it! Your original
posts implied you had a more complicated setup that needed mod_rewrite.

>I also tried the following:
>
>>RewriteCond %{HTTP_HOST} ^(.+).domain.com$ [NC]
>>RewriteRule .* http://other.domain.com/user/$1 [P]
>
>But then the browser successfully goes to the other server, but nothing
>works. Css files are not found, images not found, links not found, ...

This is because you lack a "ProxyPassReverse" to allow the
self-referentail URLs to be re-written (the ones for the images and so
on). The RewriteRule with [P] only replaces ProxyPass (although it is
much more powerful).

>My only question is if the method I use now (making for every domain a
>virtual host, and add the proxy rules in it) will take up many 
>resources
>when 300 users simultaneously use this proxy on my server.

It won't make much difference - the time taken to request and get the
resource from the downstream server is the same as if the data was on
the first server and so the only overhead you have is the time to pass
it through the proxy but this is really fast since it doesn't have to
get anything from disk - it's all passed in memory via the TCP/IP stack.

>Regards,
>
>Gunter Verbocht
>
>
>-----Original Message-----
>From: Boyle Owen [mailto:Owen.Boyle@swx.com] 
>Sent: woensdag 22 januari 2003 13:04
>To: users@httpd.apache.org
>Subject: RE: [users@httpd] Rewrite but keep original URL in browser
>
>
>
>>-----Original Message-----
>>From: Gunter Verbocht [mailto:gunter@verbocht.be]
>
>>(all in .htaccess which has is configured to overwrite all in
>>httpd.conf)
>
>The directives RewriteLog and RewriteLogLevel do not work in 
>.htaccess -
>so that's why your log doesn't get written. 
>
>>RewriteEngine On
>>Options +FollowSymlinks
>>Options -Indexes
>>RewriteBase /
>>   
>>RewriteLog "/var/log/rewrite.log"
>>RewriteLogLevel 9
>>
>># naamregistratie.be --> http://www.abcweb.nl/
>>RewriteCond %{HTTP_HOST} ^(.+).naamregistratie.be$ [NC]
>>RewriteRule .* http://www.abcweb.nl/$1 [P]
>>
>>
>>As you can also see, I receive a 500 internal server error. I 
>>also can't
>>get the rewrite log to work (I believe it should be in 
>httpd.conf but I
>>would not know where to set it, module rewrite is enabled with the
>>apache config, and apache is version: 1.3.24)
>
>You have to move:
>
>	RewriteLog "/var/log/rewrite.log"
>	RewriteLogLevel 9
>
>to httpd.conf
>
>
>
>>
>>I don't have a clue how I can find my mistake. Does anyone 
>have anymore
>>tips considering this issue?
>>
>>Regards,
>>
>>Gunter
>>
>>
>>-----Original Message-----
>>From: Boyle Owen [mailto:Owen.Boyle@swx.com] 
>>Sent: woensdag 22 januari 2003 10:56
>>To: users@httpd.apache.org
>>Subject: RE: [users@httpd] Rewrite but keep original URL in browser
>>
>>Thanks for plain text - now I can interleave the responses!
>>
>>>-----Original Message-----
>>>From: Gunter Verbocht [mailto:gunter@verbocht.be]
>>>Sent: Mittwoch, 22. Januar 2003 10:23
>>>To: users@httpd.apache.org
>>>Subject: RE: [users@httpd] Rewrite but keep original URL in browser
>>>
>>>
>>>Thank you.
>>>
>>>I have at the moment following rules in my .htaccess:
>>># domain.dom --> http://other.domain.com/user/
>>>RewriteCond %{HTTP_HOST} ^(.+\.)*domain.com$ [NC]
>>>RewriteCond %{REQUEST_URI} !http://other.domain.com/user/
>>>RewriteRule ^(.*)$ http://other.domain.com/user/$1 [P]
>>
>>I'm not an expert on mod_rewrite but I can see a few problems 
>>with this:
>>- your first RewriteCond is wrong since the regexp 
>>backreference records
>>the ".", also you don't need the "*" before "domain".
>>- You don't need the second RewriteCond at all since, to arrive in the
>>domain.com VH, you *cannot* have had a request for "otherdomain". 
>>- I don't think you need to backreference the RewriteRule at all - you
>>only need the backref from the RewriteCond.
>>
>>Putting it all together:
>>
>>RewriteCond %{HTTP_HOST} ^(.+).domain.com$ [NC]
>>RewriteRule .* http://other.domain.com/user/$1 [P]
>>
>>To debug:
>>- Look in the access log of otherdomain to see if the request is being
>>made.
>>- Activate RewriteLog to see what the rewrite engine is 
>actually doing.
>>
>>
>>>When I use this on my virtual host, I get 'page not found'. I 
>>>have on my
>>>apache webserver now proxy enabled. I will try it there, but I would
>>>like to know if the script above is correct.. or if there maybe is a
>>>better method. 
>>>
>>>
>>>Regards,
>>>
>>>Gunter Verbocht
>>>
>>>-----Original Message-----
>>>From: Boyle Owen [mailto:Owen.Boyle@swx.com] 
>>>Sent: woensdag 22 januari 2003 9:05
>>>To: users@httpd.apache.org
>>>Subject: RE: [users@httpd] Rewrite but keep original URL in browser
>>>
>>>Plain text please...
>>>
>>>You can use mod_rewrite with the [P] flag (for "proxy"). This 
>>>will cause
>>>apache to fetch the remote page and serve it directly, i.e. 
>>it will not
>>>send a redirect to the client.
>>>
>>>Alternatively, since the mapping is quite simple, you can use 
>>mod_proxy
>>>directly, e.g.
>>>
>>>ProxyPass		/  http://other.domain.com/userlogin/
>>>ProxyPassReverse	/  http://other.domain.com/userlogin/
>>>
>>>in the www.domain.com config.
>>>
>>>Rgds,
>>>
>>>Owen Boyle
>>>
>>>PS - there is a difference between redirecting and proxying; I wrote
>>>this yesterday in response to an uncannily similar question
>>>http://marc.theaimsgroup.com/?l=apache-httpd-users&m=1043138105
>>>04362&w=2
>>>-----Original Message-----
>>>From: Gunter Verbocht [mailto:gunter@verbocht.be]
>>>Sent: Dienstag, 21. Januar 2003 20:38
>>>To: users@httpd.apache.org
>>>Subject: [users@httpd] Rewrite but keep original URL in browser
>>>
>>>
>>>Hi,
>>> 
>>>I have been reading the mod rewrite guides on the apache 
>homepage, but
>>>did not find an answer.
>>> 
>>>I am looking for a solution for the following problem:
>>>I have a user with domain http://www.domain.com
>>>The user has it's webpage at url http://other.domain.com/userlogin/
>>>The url domain.com should be redirected to
>>>http://other.domain.com/userlogin but the browser bar should 
>still say
>>>http://www.domain.com
>>> 
>>>Is this possible using Apache's mod rewrite? Is their 
>another solution
>>>then using an empty frame?
>>> 
>>> 
>>>Regards,
>>> 
>>>Gunter Verbocht
>>>
>>>This message is for the named person's use only. It may contain
>>>confidential, proprietary or legally privileged information. No
>>>confidentiality or privilege is waived or lost by any 
>mistransmission.
>>>If you receive this message in error, please notify the 
>>sender urgently
>>>and then immediately delete the message and any copies of it 
>from your
>>>system. Please also immediately destroy any hardcopies of 
>the message.
>>>You must not, directly or indirectly, use, disclose, 
>>distribute, print,
>>>or copy any part of this message if you are not the intended 
>>recipient.
>>>The sender's company reserves the right to monitor all e-mail
>>>communications through their networks. Any views expressed in this
>>>message are those of the individual sender, except where the message
>>>states otherwise and the sender is authorised to state them to be the
>>>views of the sender's company. 
>>>
>>>---------------------------------------------------------------------
>>>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@httpd.apache.org
>>>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>>>For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>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@httpd.apache.org
>>>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>>>For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>
>>---------------------------------------------------------------------
>>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@httpd.apache.org
>>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>>For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>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@httpd.apache.org
>>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>>For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>
>---------------------------------------------------------------------
>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@httpd.apache.org
>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
>
>---------------------------------------------------------------------
>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@httpd.apache.org
>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>For additional commands, e-mail: users-help@httpd.apache.org
>
>

---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message