In this case the javascript provided by the sametime proxy server (running on a different node) contained relative URLs, like /stwebapi/..... Now this is not an issue when running in a production environment because we have a Webseal reverse proxy, but if you need to debug some code on a local machine then you're out of luck. The browser won't issue cross domain javascript requests.
Using Apache as a Reverse Proxy
Turns out that with a few configuration tweaks I can use apache as a reverse proxy. I added the following lines to the bottom of my \Apache2.2\conf\httpd.conf :ProxyRequests OffOrder deny,allow Allow from all ProxyPass /stwebapi http://ghprd01:9081/stwebapi ProxyPassReverse /stwebapi http://ghprd01:9081/stwebapi
So now any requests to /stwebapi will be redirected to by apache to http://ghprd01:9081/stwebapi, and as far as the browser knows it all comes from the same domain.
Piece of cake!
Found this article from IBM describing exactly how to configure reverse proxy for sametime:
ReplyDeletehttp://www-10.lotus.com/ldd/dominowiki.nsf/dx/How_to_Configure_a_Reverse_Proxy_server_for_iNotes_and_Sametime_Proxy_Integration