I wrote a custom Java element to send an HTTP request. The reason I wrote this was I wanted a "poor man's" CSS to deal with WAV files on the two media stores. I placed a test.html file in the root of the web servers and at the start of the application I would call this custom element to fetch the file from the first HTTP server. If that worked, I set a session variable that described the "default audio path". If it failed, I set the session variable to the other HTTP server.

If you have Java skills it's not that hard to write such a custom element. I used the Apache HTTP Client JAR to provide the high-level functions rather than working with the lowest level of HTTP.

If you don't have the ability to build a custom action element you may be able to work with the Web Services element - I have no experience with that one.

You may also be able to use an action element that is configured as a URI. That sends a GET that is structured in a certain way, as documented. If you control the web server you can work with the information that's sent - if you don't, then this option won't work.

I recommend the custom action element - it gives you total control without extra baggage.

Regards,
Geoff