[ic] mod_interchange

Ron Phipps rphipps at reliant-solutions.com
Mon Apr 12 00:55:42 EDT 2004


> From: interchange-users-bounces at icdevgroup.org
[mailto:interchange-users-
> bounces at icdevgroup.org] On Behalf Of Kevin Walsh
> 
> Ron Phipps [rphipps at reliant-solutions.com] wrote:
> > > > > Various features have been added to the module over its
lifetime,
> > > > > such as server failover support, request retries and further
URI
> > > > > cleanups etc.
> > > > >
> > > > But it still the case that every shop has to have a separate
catalog
> > > > name? Meaning that shop1 and shop2 can't be named www.shop1.tld
and
> > > > www.shop2.tld
> > > >
> > > Not so.
> > >
> > > Each Interchange-driven website can be identified by either its
domain
> > > name, as in your example, or by an identifier in the URI (/site1,
> > > /site2 etc.), or both.
> > >
> > Could you provide an example of the <location> settings and
> > interchange.cfg settings for an IC server running two catalog, both
> > served from "/" on different domains?
> >
> Both would use <Location /> in their respective <VirtualHost> block
> in the Apache configuration.
> 
> The interchange.cfg file would be set up something like this:
> 
>     Catalog  site1  /path/to/site1  www.foo.com/  www.foo.com:443/
>     Catalog  site2  /path/to/site2  www.bar.com/  www.bar.com:443/
> 
>     FullURL  Yes
> 
> The catalog.cfg would then be set up to make sure that any generated
> URIs use "/" as the path.
> 
> That should be all you need.
> 

Excellent, thanks for the examples.  Do you need to set
InterchangeScript for either location?

Thanks!
-Ron



More information about the interchange-users mailing list