Sure thing. All you need is a redirector helper mapping the requests
to their correct servers. But be prepared for some surprises as most
servers like to include what they think is the full URL at times..
Regards
Henrik
On Monday 17 June 2002 23.11, Tony Karakashian wrote:
> I've searched the mailing lists, and can't find anything similar to
> my needs, but I gotta assume Squid can do this thing I need. :)
>
> At home I run an IIS server, but I also have a few other services
> running on that machine that each have their own embedded web
> server running. So, obviously, they all run on different ports.
> Rather than opening up dozens of holes in my firewall, I'd like to
> setup a proxy between the outside world and this machine. I was
> thinking I could use host-headers to determine which port a request
> gets redirected to. So, for example, my home automation software
> runs on port 8000. I'd like to be able to go to, say,
> http://homeauto.myhost.com and get to the services offered there,
> rather than http://www.myhost.com:8000. I also have been playing
> with Apache/PHP on another box running Linux. I'd like to, for
> example, go to http://php.myhost.com to access the Linux box, while
> www.myhost.com accesses the IIS box. As this is a home network, I
> only have access to one IP, unfortunately...
>
> I also may have need coming up at the office for a similar setup.
> I have an application we're looking at that would require it's own
> box, but management wants it accessible via the web without any
> special instructions. I also don't want another port open on the
> firewall.
>
> Well, that's it. Hopefully, that all made sense. If not, just
> ask, I'll be sure to clarify. :)
>
> Thanks,
>
> -T
Received on Mon Jun 17 2002 - 16:47:59 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:42 MST