Thanks tim<br><br>So there are two methods to hide the second server's url - the CNAME in the case of a complete site, or Proxy for components of the second site? Although probably not ideal, couldnt you proxy everything from the second site to the first and end up with the equivalent of that of the CNAME feature?<br>
<br>In any case, the CNAME solved my issue, thanks<br><br>Shanon<br><br><br><div class="gmail_quote">On Tue, Sep 27, 2011 at 8:27 AM, Tim White <span dir="ltr"><<a href="mailto:weirdit@gmail.com">weirdit@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000">
Hi Shanon,<br>
<br>
I'm not sure if you are confused about the uses of proxyrequests and
rewrite engine?<br>
<br>
It sounds like you have a domain somewhere
(<a href="http://newexampledomain.com" target="_blank">http://newexampledomain.com</a>) that you want to server from your home
computer? You'll need to have the DNS updated to point the domain to
your home computer. If for example, your home computer is on a
dynamic ip address, and you use something like dyndns to point a
free domain to it, you can use CNAME's in DNS to point the domain to
the home computer.<br>
<br>
i.e.<br>
<br>
<a href="http://newexampledomain.com" target="_blank">newexampledomain.com</a> CNAME <a href="http://myhomecomputer.freednsprovider.com" target="_blank">myhomecomputer.freednsprovider.com</a><br>
Then you tell the apache webserver at home to listen for both domain
names (or just the newexampledomain one if you want). When a
computer accesses <a href="http://newexampledomain.com" target="_blank">newexampledomain.com</a>, it'll lookup the ipaddress
and get the CNAME, which it'll then resolve to an ip address, but
will still be using the <a href="http://newexampledomain.com" target="_blank">newexampledomain.com</a> address.<br>
<br>
Proxy requests is mainly used when you want another server to appear
as it's on the main server. For example:<br>
I have <a href="http://exampledomain.com" target="_blank">exampledomain.com</a> hosted on 1.1.1.1, but I have another
server at 2.2.2.2 that contains all my source code repository
browser (also a web server). However, I want most of my web pages
served from 1.1.1.1 except I want the 2.2.2.2 to appear like it's
also on the same server. I can then use proxyrequests so that
<a href="http://exampledomain.com/sourcecode" target="_blank">http://exampledomain.com/sourcecode</a> will actually fetch things from
the 2.2.2.2 server, not the 1.1.1.1 server. However, the client
doesn't connect to 2.2.2.2, the 1.1.1.1 server will fetch the
content from 2.2.2.2 and send it to the client. It's often used when
for example the 2.2.2.2 server is in a private network and not
publicly accessible.<br>
<br>
Lastly, rewriteengine is for changing what resource is actually
fetched from the server. So your client connects to
<a href="http://exampledomain.com/random/page/of/apples" target="_blank">http://exampledomain.com/random/page/of/apples</a> and the rewriteengine
matches some pattern and internally rewrites the address to
/myscript.php, and then myscript.php is responsible for serving the
content based on the url used.<br>
<br>
I hope that all makes a bit more sense. Please try and explain
exactly what you are trying to do (using examples of what people
type in the browser, and where you want the content to come from).<br>
<br>
Tim<div><div></div><div class="h5"><br>
<br>
On 27/09/11 01:11, Shanon Loughton wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">Hi everyone<br>
Im trying to proxy a home server to a new domain name, and I have
access to Cpanel and the .htaccess file, but not the Cpanel
httpd.conf file. <br>
<br>
As far as I can tell I have rewriteengine available to me but I
can't tell if "proxyrequests on" works? Im trying to mask the home
url address.<br>
<br>
cheers<br>
Shanon<br>
<br>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
PLUG discussion list: <a href="mailto:plug@plug.org.au" target="_blank">plug@plug.org.au</a>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a href="mailto:committee@plug.org.au" target="_blank">committee@plug.org.au</a>
PLUG Membership: <a href="http://www.plug.org.au/membership" target="_blank">http://www.plug.org.au/membership</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.org.au">committee@plug.org.au</a><br>
PLUG Membership: <a href="http://www.plug.org.au/membership" target="_blank">http://www.plug.org.au/membership</a><br></blockquote></div><br>