Another way to workaround the first problem is to set up virtual hosts on
your A4D server (a4d.mysite1.com, a4d.mysite2.com) and use host-specific
rewrite rules on the WebSTAR server to proxy the requests to the appropriate
A4D site.
Derrell,
Can you elaborate on this more?
In my case WebSTAR and Active4D reside on the same machine. All of my WebSTAR to Active4D proxies go to 127.0.0.1:8080.
You can create your own fake domain names by putting them in the hosts file. On Mac OS X, it's /etc/hosts, on Windows it's \Windows\System32\drivers\etc\hosts. So you can add entries like this:
127.0.0.1 a4d.mysite1.com 127.0.0.1 a4d.mysite2.com
They both point to your box, but if you use those names as the host in a WebSTAR proxy request, the hostname you use will be accessible to Active4D and thus to virtualhosts.ini.
Regards,
- Aparajita
_______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
