Jon, For what I know by default it will use the browser's network stack unless you go out of browser or explicitly change to use the other one. However, what you're experiencing looks like symptoms of using the new stack.
Check this post: http://developers.de/blogs/damir_dobric/archive/2009/08/22/soap-faults-and-new-network-stack-in-silverlight-3.aspx To enable it use this line of code: bool registerResult = WebRequest.RegisterPrefix("http://";, WebRequestCreator.ClientHttp); He explains the difference and the drawback, look at the last paragraph. Silverlight 3 provides the “client HTTP stack” which, unlike the “browser HTTP stack”, allows you to process SOAP-compliant fault messages. However, a potential problem of switching to the alternative HTTP stack is that information stored by the browser (such as authentication cookies) will no longer be available to Silverlight, and thus certain scenarios involving secure services might stop working, or require additional code to work. For more information, see HttpCookieContainerBindingElement<http://msdn.microsoft.com/en-us/library/system.servicemodel.channels.httpcookiecontainerbindingelement%28VS.95%29.aspx>. *I figured out that windows authentication which has been used in my services does not work anymore by using of new network stack. By default service proxies at the client do not send required authentication headers.* On Mon, Nov 30, 2009 at 4:39 PM, John OBrien <[email protected]>wrote: > Has anyone had this problem before? > > I have a Silverlight 2 application running fine, fully upgraded to > Silverlight 3 and now from behind a proxy server all my WCF requests are > getting 407 errors, the old Silverlight 2 site still work fine. > > > > The client is pretty sure their proxy is using AD to authenticate access to > the internet and my application is using forms authentication to allow > access to the asp.net page hosting the XAP and the service has this > attribute: > > [AspNetCompatibilityRequirements(RequirementsMode = > AspNetCompatibilityRequirementsMode.Allowed)] > > > > My guess is it’s something with the new network stack in Silverlight3 and > authentication but I’m not finding much info and can’t replicate the > environment from here. > > > > Hoping someone here has seen this before. > > John. > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > -- Miguel A. Madero Reyes www.miguelmadero.com (blog) [email protected]
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
