RE: [us...@httpd] Rewrite Voodoo pt. 2

I love chocolate chip cookies From: Reese [howel...@inkworkswell.com] Sent: Tuesday, January 26, 2010 8:06 PM To: users@httpd.apache.org Subject: Re: [us...@httpd] Rewrite Voodoo pt. 2 ... If you were local to me, I'd offer you a cookie. Chocolate chi

RE: [us...@httpd] Rewrite Voodoo pt. 2

> Can you interpret: >> >> rewriteCond $(HOST_NAME) ^(.*)\.domain\.ext > > Condition, proceed for host_name matching (anySubdomain).domain.ext > >> rewriteRule ^(.*)$ $(HOST_NAME)$1 > > Rule, I'm not sure what it does. Based on the link Tom posted, I'd > guess that it takes everything after

RE: [us...@httpd] Rewrite Voodoo pt. 2

> >> My attempt was: >> >> RewriteEngine On >> RewriteRule ^(www\.)?domain\.ext/subdomain/(.*)$ >> subdomain\.domain\.ext/$2 [R=301,L] >> >> I now think this would be better: >> >> RewriteEngine On >> RewriteRule ^domain\.ext/subdomain/(.*)$ subdomain\.domain\.ext/$2 >> [R=301,L] > > No

RE: [us...@httpd] Rewrite Voodoo pt. 2

Reese wrote: > > It tells me that the part after the host (I want to change the host > name) and the part after the query string (that I'm not using if I > understand the usage) are tips of the iceberg. And that is the part > I'm trying to understand. And neither Tom nor you are helping. > > Did I

RE: [us...@httpd] Re: Apache vs LiteSpeed

> From: LuKreme [mailto:krem...@kreme.com] > Sent: January 15, 2010 11:45 AM > > On 15-Jan-2010, at 09:29, Jarrod Slick wrote: > > I'm curious -- why do you think that the results will be > inconsistent? If anything I would be inclined to think that using > localhost would improve consistency as

RE: [us...@httpd] RewriteRule and VirtualDocumentRoot: How do they interract ?

> From the doc : > > > This flag is just a hack to enable post-processing of the output of > RewriteRule directives, using Alias, ScriptAlias, Redirect, and other > directives from various URI-to-filename translators > > If I understand well (correct me if I'm wrong), after RewriteRule has > app

RE: [us...@httpd] :Mod rewrite

> From: Marcin 'Rambo' Roguski [mailto:ra...@id.uw.edu.pl] > > > Marcin, I'm also curious about your statement about security hole when > > spoofing a domain name via mod-rewrite. Isn't mod-rewrite *all* about > > spoofing URL's (which can include domain name part)? > > As you mentioned, remappin

RE: [us...@httpd] Mod_Rewrite voodoo

> From: Reese [mailto:howel...@inkworkswell.com] > > >> I tried: > >> > >> RewriteEngine On > >> RewriteCond %{HTTP_HOST} subdomain\.domain\.ext > >> RewriteCond %{REQUEST_URI} ^/20\d+ > >> RewriteRule (.*)(0[5-9]).html$ /20$2/$1$2.html [R=301,L] > >> > >> For http://subdomain.domain.ext/fileDDMMY

RE: [us...@httpd] :Mod rewrite

> From: Marcin 'Rambo' Roguski [mailto:ra...@id.uw.edu.pl] > > >> Instead of display a dummy url : > >> http://s1.ncs.com/inventoryappl > > > spoofing DNS, I'm not at all sure what he was talking about > > From my understanding the question was if one can hide real url and > display a fake one

RE: [us...@httpd] URL re-writing problem

Vijay, If you have a small number of subdomains, I would try, for each one: ServerName subdomainN.domain.com ProxyRequests off ProxyPass / http://domain.com/key/subdomainN ProxyPassReverse / http://domain.com/key/subdomainN Otherwise I would try a rewrite rule such

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

>> 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

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

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

[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