views:

33

answers:

2

I've got a Silverlight application that makes a cross-domain request. The clientaccesspolicy.xml file exists on the server I am making a request to and is correctly configured.

I know that it is correctly configured because when I use the application to make a request from my machine I receive a response with no problem.

When a second individual on a corporate network about 300 miles away tries to use the same application, launched from the same URL, to make the same request, he instead gets a security exception.

Here's the odd part. I requested that he download Fiddler so that I could see the request and it's response, and thereby gain some insight into the problem, but when he runs the app with Fiddler open, the request succeeds.

This happens in both Chrome and IE. With Fiddler everything is fine. Without it, it doesn't work.

We've tried clearing his history, deleting the Silverlight app from the cache, everything I can think of.

The request is being made to a private network (which he is on), I make the request through a VPN connection to that network (in case for some reason that matters).

Any thoughts as to what's causing this bizarre problem?

A: 

Despite the fact the Fiddler "fixes" the issue it would still be worth while getting this second individual to save a .saz file from fiddler for the successfull set of sessions and then for you to compare them with a successfull set you have from your own machine.

An analysis of the differences may reveal a potential cause when fiddler is not in place.

Another approach would be to use a network protocol anaylser such as Wireshark. The elimination of the proxy that Fiddler represents may be enough to expose the problem, of course such tool is much more technical.

AnthonyWJones
He should be sending me his .saz file soon. Once I get it and analyze it I'll update the OP with any information I can glean from it.
Anthony Compton