Situation:

I am developing a Silverlight-Application which needs Component based on a local HTTP Listener.

The HTTP-Listener can't be 'required' to be installed and running when the Application starts, so the Application does the following:

• Handshake via HTTP POST
• If Connection failed open a Click-Once Setup to install the component.

So far so good.... now the Problem is:

If the HTTP POST for the Handshake fails, because the Listener is not running the POST is cached.... and the following Connection Attempts after the Service is running fail, because the HTTP POST is still in Cache after the first try.

NOTE: This is NOT a policy-problem.

I'm using SL4

PS: I allready tried adding a random parameter to the URL like

First try: Second try:

didn't work :-(