RE: MSProxy talking to Squid?

I don't know about V 1, I've only used V2.
-Vince

>
> How about MS Proxy V1?
>
> On Wed, 10 Mar 1999, Vincent Romeo wrote:
>
> > In short, it is possible. I don't think MS Proxy actually
> speaks ICP, but
> > you can get it to forward web requests to upstream non-MS
> proxies. Relevant
> > info from MS Proxy docs follows.
> >
> > Vince Romeo, Systems Manager
> > Madison Academy
> > vjromeo@bigfoot.com
> >
> > >From the MS Proxy docs:
> >
> > Configuring Proxy Server Routes
> > You can administer Proxy Server routes from the Web Proxy
> service. Web Proxy
> > client requests can be routed within an array, to an upstream
> Proxy Server
> > or Proxy Server array, or directly to the Internet. Client
> requests can also
> > be resolved first within an array before routing the request upstream.
> >
> > The routing algorithm automatically detects the operating status of the
> > Proxy Server computer in the upstream chained configuration. In
> addition,
> > array membership changes can be detected, both within an array
> or upstream.
> > If you are not using the Web Proxy service, upstream routing should be
> > disabled.
> >
> > Note Only Web Proxy client requests can be routed through
> chained Proxy
> > Server computers or Proxy Server arrays. The WinSock Proxy and
> Socks Proxy
> > services do not support chained requests.
> >
> > Upstream Routing
> > You can route a Web Proxy client request upstream to a Proxy Server
> > computer, Proxy Server array, or directly to the Internet. If you are
> > routing to an upstream Proxy Server computer or Proxy Server
> array, you can
> > use authentication.
> >
> > You can specify a backup or alternate route if a chained computer is
> > unavailable or malfunctioning. This provides an automatic
> transfer, thereby
> > eliminating a single point of failure. The backup route is
> fully functional
> > and supports all routing configurations that the primary route supports.
> > After switching to the backup route, the unresponsive Proxy
> Server computer
> > is queried until it's available again, at which time the
> primary route is
> > automatically reestablished.
> >
> > The following procedure configures the primary upstream routing
> properties
> > used under normal conditions. You can also configure a backup route if a
> > client request cannot be successfully routed by using the primary route.
> > After configuring the upstream routing properties, you should
> next define
> > the primary upstream route by clicking Modify.
> >
> > To configure upstream routing properties
> > In Internet Service Manager, double-click the computer name
> next to the Web
> > Proxy service.
> > In the Web Proxy Service Properties dialog box, click the Routing tab.
> > Under Use this Http Via Header alias for the local server, enter a valid
> > computer name that will be used in the HTTP header for all requests.
> > Under Upstream Routing, do one of the following:
> > To route all Web Proxy client requests directly the Internet, click Use
> > direct connection.
> > To route all Web Proxy client requests upstream to another Proxy Server
> > computer or array, click Use Web Proxy or array.
> > To use a backup upstream route, verify that the Enable backup
> route check
> > box is selected, and do one of the following:
> > To route all Web Proxy client requests directly the Internet, click Use
> > direct connection.
> > To route all Web Proxy client requests upstream to another Proxy Server
> > computer or array, click Use Web Proxy or array.
> > Click Apply, and then click OK.
> > You can use the following procedure to configure the primary
> upstream route.
> > You can enable automatic polling of upstream Proxy Server computers for
> > their array membership information. You can also set user
> credentials for
> > upstream routing. This means you can create Proxy Server-to-Proxy Server
> > authentication credentials from a downstream Proxy Server computer to an
> > upstream Proxy Server computer.
> >
> > Note The array URL is automatically generated from the Proxy Server
> > computer name you type. You are not required to change this URL if the
> > upstream computer is running Microsoft Proxy Server Version 2.0.
> >
> > To configure the primary upstream route
> > In Internet Service Manager, double-click the computer name
> next to the Web
> > Proxy service.
> > In the Web Proxy Service Properties dialog box, click the Routing tab.
> > Under Upstream Routing, verify that the Use Web Proxy or array option is
> > selected, and then click Modify.
> > In the Advanced routing options dialog box, under Upstream Web
> Proxy Server,
> > in Proxy, type a valid server name or array name, and in Port,
> type a valid
> > port number (usually port 80).
> > Verify that the Auto-poll upstream proxy for array
> configuration check box
> > is selected, and then select the Use credentials to communicate with
> > upstream proxy/array check box.
> > In Username, type a valid user name, and in Password, type a
> valid password.
> > To enable basic authentication, click Allow basic/clear text
> authentication.
> > To enable Windows NT challenge/response authentication, click Allow
> > encrypted authentication (NT CR).
> > Click OK, click Apply, and then click OK again.
> > You can use the following procedure to configure a backup
> upstream route if
> > the primary route fails. You can enable automatic polling of
> upstream Proxy
> > Server computers for their array membership information. You
> can also set
> > user credentials for upstream routing. This means you can create Proxy
> > Server-to-Proxy Server authentication credentials from a
> downstream Proxy
> > Server computer to an upstream Proxy Server computer.
> >
> > Before you can configure a backup upstream route, you must
> first configure a
> > primary upstream route to connect to a chained upstream Proxy Server
> > computer or array.
> >
> > Note The array URL is automatically generated from the Proxy Server
> > computer name you type. It is recommended that you do not
> change this URL.
> > You are not required to change this URL if the upstream
> computer is running
> > Microsoft Proxy Server Version 2.0.
> >
> > To configure the backup upstream route
> > In Internet Service Manager, double-click the computer name
> next to the Web
> > Proxy service.
> > In the Web Proxy Service Properties dialog box, click the Routing tab.
> > Under Upstream Routing, verify that the Enable backup route
> check box and
> > the corresponding Use Web Proxy or array option are both
> selected, and then
> > click Modify.
> > In the Advanced routing options dialog box, under Upstream Web
> Proxy Server,
> > in Proxy, type a valid server name or array name, and in Port,
> type a valid
> > port number (usually port 80).
> > Verify that the Auto-poll upstream proxy for array
> configuration check box
> > is selected, and select the Use credentials to communicate with upstream
> > proxy/array check box.
> > In Username, type a valid user name, and in Password, type a
> valid password.
> > To use basic authentication, verify that Allow basic/clear text
> > authentication is selected.
> > To enable Windows NT challenge/response authentication, click Allow
> > encrypted authentication (NT CR).
> > Click OK, click Apply, and then click OK again.
> >
> > > -----Original Message-----
> > > From: Bill Wichers [mailto:billw@unix0.waveform.net]
> > > Sent: Wednesday, March 10, 1999 12:26 PM
> > > To: squid-users@ircache.net
> > > Subject: MSProxy talking to Squid?
> > >
> > >
> > > I know this has been asked before, and I'm sure I've even
> seen it, but now
> > > I need the info and the searchable archive is down! Spare a moment and
> > > give me a quick email reply and I'd really appreciate it!
> > >
> > > All I need to know is if it is possible to get an MSProxy box
> to talk to
> > > use a Squid box as a parent. I think this is no problem, but MS's site
> > > says absolutly nothing about using their proxy with anyone
> else's proxy.
> > > They also don't say anything about ICP and such, if it even
> supports it. I
> > > know they use CARP between other MSProxy boxes.
> > >
> > > TIA
> > >
> > > -Bill
> > >
> >
> >
>
Received on Thu Mar 11 1999 - 11:18:33 MST