kevin at cursor.biz
Sun Apr 11 03:51:52 EDT 2004
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/
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.
_/ _/ _/_/_/_/ _/ _/ _/_/_/ _/ _/
_/_/_/ _/_/ _/ _/ _/ _/_/ _/ K e v i n W a l s h
_/ _/ _/ _/ _/ _/ _/ _/_/ kevin at cursor.biz
_/ _/ _/_/_/_/ _/ _/_/_/ _/ _/
More information about the interchange-users