I'm worried that there may be issues that I have not thought
of/discovered and am throwing this out to the list in hopes on
avoiding any unpleasant surprises.
I'm planning on implementing a "virtual hosting" scheme in a single
aolServer process based on host headers. We provide the same basic
service to all of our customers. Currently we support multiple
customers on a single "host" (same URL). I want to be able to provide
a different URL to each customer, still hitting the same pages. We
already provide service to multiple clients out of a single Oracle
schema, so there are no database pool issues.
Things I know will break:
ns_returnredirect puts what it thinks is the "right" hostname in when
the URL argument starts with "/". I can fix that by making a proc to
stick in what *I* think is the right hostname (based on the host
header) in those cases and then calling ns_returnredirect. Then I
never call ns_returnredirect directly again. (I could change the C
code, but I want to avoid making changes at that level if possible.)
SSL: we're not doing SSL on our servers currently. I'm wondering how
difficult (impossible?) it will be to "hack" aolserver so that I can
have multiple SSL configs within a single aolServer process based on
the host header.
Cookies: I plan to have a list of "aliases" for each "canonical"
hostname. A registered filter will redirect to the canonical hostname
when we receive a GET request with a host header of one of the
aliases. This should keep browsers on the right path, and away from
the aliases (and thus the cookies set to the right hostnames).
Am I missing anything?
--
Patrick Kelly -- http://www.oakroad.net/patrick.html
