The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: URL Rewriting in Apache anyone?



Tony,

Not quite, the apache server at mydomain.com will respond to the browser
with a redirect response pointing it to the webserver at home on port 8080,
as such youll need to open port 8080 through your firewall.  now if you are
with Mr Bond and he is feeling generous you could use the squid proxy server
as a web site accelerator which a: speeds up performance but more important
b: means you only need a single IP address to access the ports at home which
means you keep a fair degree of security on your firewall.

In effect your mydomain.com points to a proxy server not a real web server.
the proxy then talks to your webservers for you and as such you only need
one point of access to your range of services

the squid config file is 10000 lines long so you better hope Mr Bond is
generous ;-)

k.


-----Original Message-----
From: BUTLER, Tony, FM [mailto:roaming@xxxxxxx]
Subject: RE: [ukha_d] URL Rewriting in Apache anyone?

Wow - that simple eh?  Will this appear transparent to the end user?
ie, when I type in tivo.mydomain.com, it _must_ only talk over port 80 to
the mydomain.com server, which then itself will talk over 8080 to the
destination.  The client cannot in reality be talking over 8080 itself,
thanks to firewall restrictions :-(

cheers,


Tony


http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.