Re: about the absolutely path
| From: | Burhan Khalid | Date: | Tue, 07 Jun 2005 06:30:13 +0000 |
| Subject: | Re: about the absolutely path | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-216543@lists.php.net to get a copy of this message | ||
Jochem Maas wrote:
Richard Lynch wrote:I've been trying to search for that message for a while. It talked about running php4 and php5 in one Apache instance.On Mon, June 6, 2005 1:54 am, yangshiqi said:maybe you could use the apache ProxyPass directive? ProxyPass testb.xxx.com/a/ testa.xxx.com or something like that. (I'm just half-remembering a cool post by Rasmus L. so the syntax is probably off)I have a php application (let's call it app A) which is developed separated in a test domain name, like http://testa.xxx.com <http://testa.xxx.com/> /. But now I have to move it to another app (called B) using http://testb.xxx.com <http://testb.xxx.com/> /, and the app A becomes just a subsystem of app B. The access url is changed to http://testb.xxx.com/a/. Then I meet a problem that the app A 's links, the path and other elements in it are set like '/Main.php', '/art/logo.gif' by an absolutely path. The app A is very independent and I do not want to disperse it to app B. So how can I get this effect: when the user input the url, ' http://testb.xxx.com/a/ ', the app A will work fine? Can I just modify some configuration about yapache to fit this requirement?