Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 50856 invoked by uid 500); 5 Mar 2003 12:20:14 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 50842 invoked from network); 5 Mar 2003 12:20:14 -0000 Received: from ms-smtp-01.tampabay.rr.com (65.32.1.43) by daedalus.apache.org with SMTP; 5 Mar 2003 12:20:14 -0000 Received: from michaelk1 (rrcs-se-24-73-170-130.biz.rr.com [24.73.170.130]) by ms-smtp-01.tampabay.rr.com (8.12.5/8.12.5) with ESMTP id h25CK60B027663 for ; Wed, 5 Mar 2003 07:20:13 -0500 (EST) From: "Michael Klama" To: Date: Wed, 5 Mar 2003 07:20:05 -0500 Message-ID: <000801c2e311$8e6e2ed0$6501a8c0@michaelk1> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] problem configuring mod_rewrite rule Hello Owen, I was incorrect in my previous statement that said the rewrite was = working correctly and I was getting a permissions error. I spent about 6 hours = last night trying to figure out exactly what is going on by changing the = rewrite rule and watching the logs. What I was able to determine was exactly = what Jurgen wrote in his post yesterday. The rewrite condition is being = matched, REMOTE_USER and the file path is being rewritten to the same document = root that it was before the condition was matched. Now I need to figure out = how to change the file path from that point so my client is taken to their proper directory. In answer to your questions you posted What The User Types: client web site administrators. This rewrite will = take them to a page that is customized to their domain What The URL Should Change To: I am not so concerned with changing the = URL. If it can be changed, fine, if not, fine. My concern is changing the = file path to the page that is customized for their domain. In this = particular case I am working on the document root for users.mrktechweb.com is /home/users/web/ and this rewrite needs to change that to /home/users/web/mrktechweb/ based on RewriteCond REMOTE_USER. Another different domain admin will type in the same URL users.mrktechweb.com = and will be taken to his particular directory /home/users/web/hisdomain/. I will put in a rewrite rule and condition for each domain that I have on = my server so each site admin can access their own customized page in their = own particular directory beneath the users.mrktechweb.com document root. Last night I also discovered that the permission error I was getting was = due to the fact that the file path was not being rewritten and I was ending = up in the same document root /home/users/web/ which did not contain an = index file and I do not have directory indexing turned on on this server. I hope I have explained all of this properly and this will be useful in = your response. Mike -----Original Message----- From: Boyle Owen [mailto:Owen.Boyle@swx.com]=20 Sent: Wednesday, March 05, 2003 3:03 AM To: users@httpd.apache.org Subject: RE: [users@httpd] problem configuring mod_rewrite rule >-----Original Message----- >From: Michael Klama [mailto:nosedive@tampabay.rr.com] > >Owen, >I used the rule that you inserted below RewriteRule /(.*) >/mrktechweb/$1/index.htm and changed it to read /(.*) >$1/mrktechweb/index.htm and it actually rewrote the url=20 >correctly in the >browser but I still get the error that I do not have=20 >permission to access / >on this server. Any ideas? So you have a different problem. I'm still not entirely clear what you = are trying to achieve because you haven't given a clear example. Can you = please fill in the blanks (note - URLs, not filepaths). What The User Types: What The URL Should Change To: (Give several examples rather than using wildcard variable strings and = so on...) Since you are not using a [P] flag, I guess you are happy with = mod_rewrite generating redirects. Therefore the rewritten URL must be visible from = the client. So what happens if you bypass mod_rewrite and try to access the final URL directly from the client? I guess you get the "permission" = problem (BTW, I am assuming you mean a "403 Forbidden" - it would be helpful if = you always quote the HTTP status code and its official title instead of paraphrasing it). In that case, the problem is that access to the destination URL is = "Deny"-ed somewhere. Check in the error_log for "access denied by server configuration"... Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored.=20 > >Mike=20 > >-----Original Message----- >From: Boyle Owen [mailto:Owen.Boyle@swx.com]=20 >Sent: Tuesday, March 04, 2003 10:31 AM >To: users@httpd.apache.org >Subject: RE: [users@httpd] problem configuring mod_rewrite rule > >>-----Original Message----- >>From: Michael Klama [mailto:fvimike@earthlink.net] >> >>Thank you for your response Owen. I am in meetings all day=20 >>long so will not >>be able to try this until this evening. If I am not mistaken,=20 >>what you are >>saying is that this rule will append the original root=20 >>directory onto the >>end of what I am trying to change the directory too. This is=20 >>not what I intended. =20 > >I guessed that...=20 > >>What I intended is to take the request which goes=20 >>to the root >>directory of this web and at the point that it reaches that=20 >>root directory, >>is changed to point to a lower directory which is inside the=20 >>root directory based on the REMOTE_USER condition. > >Ummm... I'm a bit lost in the subordinate clauses here (an=20 >example might be >useful...) Usually, you use mod_rewrite to map a simple=20 >webspace (visible to >the client) to a more complicated internal webspace, e.g. > > /foobar --> /mrtechweb/foobar/index.html > >to do that, use; > > RewriteRule /(.*) /mrktechweb/$1/index.htm > >Is this closer to what you had in mind? > >Rgds, >Owen Boyle >Disclaimer: Any disclaimer attached to this message may be ignored.=20 > >> >>Thanks >>Mike >> >> >>-----Original Message----- >>From: Boyle Owen [mailto:Owen.Boyle@swx.com] >>Sent: Tuesday, March 04, 2003 8:57 AM >>To: users@httpd.apache.org >>Subject: RE: [users@httpd] problem configuring mod_rewrite rule >> >>>-----Original Message----- >>>From: Michael Klama [mailto:nosedive@tampabay.rr.com] >>> >>>RewriteEngine on >>>RewriteCond %{REMOTE_USER} ^mike.* >>>RewriteRule (/*) /mrktechweb/index.htm$1 >> >>Try: >> >> RewriteRule (/.*) /mrktechweb/index.htm$1 >> >>It's a subtle difference but mod_rewrite uses regexp, it's=20 >not Perl ;-) >> >>By the way, this will rewrite /foo.bar as /mrktechweb/index.htmfoo.bar >>which is a bit funny.... >> >>Rgds, >>Owen Boyle >>Disclaimer: Any disclaimer attached to this message may be ignored. >>> >>> >>>(2) init rewrite engine with requested uri /mrktechweb/index.htm >>>(1) pass through /mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] strip per-dir prefix: >>>/home/users/web/mrktechweb/index.htm -> mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] applying pattern '(/*)' to uri >>>'mrktechweb/index.htm' >>>(4) RewriteCond: input=3D'mike' pattern=3D'^mike.*' =3D> matched >>>(2) [per-dir /home/users/web/] rewrite mrktechweb/index.htm -> >>>/mrktechweb/index.htm >>>(1) [per-dir /home/users/web/] internal redirect with >>>/mrktechweb/index.htm >>>[INTERNAL REDIRECT] >>>(2) init rewrite engine with requested uri /mrktechweb/index.htm >>>(1) pass through /mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] strip per-dir prefix: >>>/home/users/web/mrktechweb/index.htm -> mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] applying pattern '(/*)' to uri >>>'mrktechweb/index.htm' >>>(4) RewriteCond: input=3D'mike' pattern=3D'^mike.*' =3D> matched >>>(2) [per-dir /home/users/web/] rewrite mrktechweb/index.htm -> >>>/mrktechweb/index.htm >>>(1) [per-dir /home/users/web/] internal redirect with >>>/mrktechweb/index.htm >>>[INTERNAL REDIRECT] >>>(2) init rewrite engine with requested uri /mrktechweb/index.htm >>>(1) pass through /mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] strip per-dir prefix: >>>/home/users/web/mrktechweb/index.htm -> mrktechweb/index.htm >>>(3) [per-dir /home/users/web/] applying pattern '(/*)' to uri >>>'mrktechweb/index.htm' >>>(4) RewriteCond: input=3D'mike' pattern=3D'^mike.*' =3D> matched >>>(2) [per-dir /home/users/web/] rewrite mrktechweb/index.htm -> >>>/mrktechweb/index.htm >>>(1) [per-dir /home/users/web/] internal redirect with >>>/mrktechweb/index.htm >>>[INTERNAL REDIRECT] >>> >>>As you can see this just goes on and on and on. I gets to the >>>point where >>>it will completely hang up everything on my server. Thank you >>>to all who >>>can help >>> >>>Mike >>> >>> >>> >>>--------------------------------------------------------------------- >>>The official User-To-User support forum of the Apache HTTP >>>Server Project. >>>See 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 >>> >>> >> >>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=20 >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,=20 >distribute, print, >>or copy any part of this message if you are not the intended=20 >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=20 >>Server Project. >>See 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=20 >>Server Project. >>See 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=20 >Server Project. >See 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=20 >Server Project. >See 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 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 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