you could use different ips for the two services. on the external ip run apache, on the internal one squid. note that you wont be able to use www.mydomain.com:80 for both services.
suggestion : www.mydomain.com:80 -> external ip internal.mydomain.com:80 -> internal ip the internal ip should be accessable only from the internal network. yours josef On Fri, 2003-02-14 at 11:28, Jon Haugsand wrote: > * Jordi Curià > > JH> And exactly what would you like to happen when a tcp request is made > > JH> to your computer on port 80? Should it go to squid or should it go to > > JH> apache? > > > > > > > > I want to share the port 80 with squid and apache, I don't know if > > it's posible. I want to use squid on port 80 and I want to use a > > intranet web like http:///www.mydomain.com. Now I'm rounning de apache > > in other port like http://ww.mydomain.com:81 > > You didn't answer my question. What should happen when any http > request (i.e. tcp request) is flowing into your machine destined for > port 80? What do you HOPE should happen? > > 1. Routed to squid > 2. Routed to apache > 3. Duplicated and routed to both > 4. Routed to any tossing a coin > 5. Inspecting the request and the psychological profile of the > requester and routed to the server that his brain would like to > handle it. > > If you want to let squid handle all outgoing requests and apache all > local requests, I do not know if this is possible, but why can't you > do as you do, put apache on one port and squid on another and instruct > squid to send locally all local requests? > > -- > Jon Haugsand, [EMAIL PROTECTED] > http://www.norges-bank.no > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
