> You'll most likely use the Rewrite module to forward (proxy) your request > onto Active4D. It works well but that there is a bug in the Rewrite module > where host and other information such as "www.mysite1.com" and > "www.mysite2.com" is lost in the proxy. Therefore, when Active4D tries to > see where the original request was meant to go it sees it as 127.0.0.1 (or > maybe "localhost"). There is a workaround, but is IMO it is a kludge and a > big PITA. You have to append query params such as ?host="mysite1.com" etc. > to all your proxied requests. Your Active4D pages have to be programmed to > look for these params and react accordingly. It's not difficult to do, but > you have to be aware of this bug, and deal with it in all cases where it > might affect your development. > > There is another bug in the rewrite module where if your Active4D pages (or > any destination proxy) isn't running, WebSTAR will simply serve a blank > page instead of alerting the user that the proxy failed. > > 4D Inc. is aware of these bugs, but there is no ETA on a fix (last time I > asked). I'm bringing it up here to renew attention to these issues.
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. As for the second bug, I'm with you all the way on this one. I HATE the fact that "upgrading" from WebSTAR 4 to WebSTAR V caused me to lose the ability to display a "temporarily unavailable" page when the A4D server was down. -- // Derrell Thomason // Desktop Programming Coordinator // Pensacola Christian College <http://www.pcci.edu/> _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
