RE: [us...@httpd] best way to modify a URL

From: André Warnier [...@ice-sa.com] >>> Considering your latest answer, I am also now inclined to think that >>> using sections would be much cleaner. >> >> More efficient, more maintainable, or less code to write to obtain same >> effect? >> > Probably all of the above. > General idea : What

Re: [us...@httpd] best way to modify a URL

2. major issue: form POST problem: form POST should probably not get redirected either, but so far I can't find what condition to test for Purely as an aside : Redirecting a POST internally is not a problem, because it happens early, before Apache even starts to read the request body (so to

Re: [us...@httpd] best way to modify a URL

Oliver Schoenborn wrote: RewriteCond %{HTTP_HOST} ^dodo\.foo\.com$ RewriteRule ^/bar/(.*) /$1[R,L] RewriteCond %{HTTP_HOST} ^dodo\.foo\.com$ RewriteRule ^(.+)%{HTTP_HOST}$1 [C] RewriteRule ^dodo\.foo\.co

RE: [us...@httpd] best way to modify a URL

>> RewriteCond %{HTTP_HOST} ^dodo\.foo\.com$ >> RewriteRule ^/bar/(.*) /$1[R,L] >> >> RewriteCond %{HTTP_HOST} ^dodo\.foo\.com$ >> RewriteRule ^(.+)%{HTTP_HOST}$1 [C] >> RewriteRule ^dodo\.foo\.com/(.*)

Re: [us...@httpd] best way to modify a URL

Oliver Schoenborn wrote: In order to apply the proxying just for dodo.foo.com only, I use a rewrite rule. Here is what I have so far, seems to work completely: RewriteCond %{HTTP_HOST} ^dodo\.foo\.com$ RewriteRule ^/bar/(.*) /$1[R,L] RewriteCond %{HTTP

RE: [us...@httpd] best way to modify a URL

Thanks Andre for the detailed explanations. Looks like I have it figured out: From: André Warnier [...@ice-sa.com] >> >> 1. Client goes to http://dodo.foo.com: >> A. server changes this to http://foo.com/bar >> B. server returns content (which will be http://foo.com/bar/index.html) >> C. cl

Re: [us...@httpd] best way to modify a URL

Much, much better, and really clear this time. Oliver Schoenborn wrote: Sorry I didn't notice the html format, I'm amazed that some people were able to understand my question! (only the smart ones) Hopefully it works now. Here is what I am trying to do, 2 separate cases: 1. Client goes to h

RE: [us...@httpd] best way to modify a URL

o:just...@newmediagateway.com] > Sent: December 15, 2009 6:14 PM > To: users@httpd.apache.org > Subject: Re: [us...@httpd] best way to modify a URL > > Oliver Schoenborn wrote: > > > > I have a simple problem: the URL root for a client website we are > > setting up

RE: [us...@httpd] best way to modify a URL

eas how to remove that step? For #2, perhaps a redirect rule? Oliver > -Original Message- > From: André Warnier [mailto:a...@ice-sa.com] > Sent: December 15, 2009 5:59 PM > To: users@httpd.apache.org > Subject: Re: [us...@httpd] best way to modify a URL > > Oliv

Re: [us...@httpd] best way to modify a URL

Oliver Schoenborn wrote: I have a simple problem: the URL root for a client website we are setting up is http://foo.com/bar/*, but our client wants access to be it via http://dodo.foo.com /*, how would I set this up? I have used mod_proxy in the past for something similar

Re: [us...@httpd] best way to modify a URL

Oliver Schoenborn wrote: I have a simple problem: the URL root for a client website we are setting up is http://foo.com/bar/*, but our client wants access to be it via http://dodo.foo.com /*, how would I set this up? I have used mod_proxy in the past for something similar

Re: [us...@httpd] best way to modify a URL

Oliver Schoenborn wrote: I have a simple problem: the URL root for a client website we are setting up is http://foo.com/bar/*, but our client wants access to be it via http://dodo.foo.com/*, how would I set this up? I have used mod_proxy in the past for something similar

[us...@httpd] best way to modify a URL

I have a simple problem: the URL root for a client website we are setting up is http://foo.com/bar/*, but our client wants access to be it via http://dodo.foo.com/*, how would I set this up? I have used mod_proxy in the past for something similar but this doesn't seem to be