Hey John,

Your best bet is to fiddler or charles your silverlight 3 app (sitting behind 
the proxy) to see what network traffic is going out and comming in (if at all).

My guess is the new SL3 networking stack and how it now does url resolution 
(between sl2 and sl3) may be the cause. BUT again just guessing.

Fiddler should point you in the right direction.

________________________________________
From: [email protected] 
[[email protected]] On Behalf Of 
[email protected] 
[[email protected]]
Sent: Tuesday, 1 December 2009 10:53 AM
To: [email protected]
Subject: ozsilverlight Digest, Vol 4, Issue 1

Send ozsilverlight mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ozsilverlight digest..."


Today's Topics:

   1. Silverlight 3 getting 407 proxy auth errors? (John OBrien)
   2. Re: Silverlight 3 getting 407 proxy auth errors? (Miguel Madero)
   3. Our new silverlight site (Ross McKinnon)
   4. RE: Our new silverlight site (Nick Randolph)


----------------------------------------------------------------------

Message: 1
Date: Mon, 30 Nov 2009 15:39:41 +1000
From: "John OBrien" <[email protected]>
Subject: Silverlight 3 getting 407 proxy auth errors?
To: "'ozSilverlight'" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://prdlxvm0001.codify.net/pipermail/ozsilverlight/attachments/20091130/2d398ff1/attachment-0001.html

------------------------------

Message: 2
Date: Mon, 30 Nov 2009 22:47:31 +1100
From: Miguel Madero <[email protected]>
Subject: Re: Silverlight 3 getting 407 proxy auth errors?
To: ozSilverlight <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="windows-1252"

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]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://prdlxvm0001.codify.net/pipermail/ozsilverlight/attachments/20091130/0b46697d/attachment-0001.html

------------------------------

Message: 3
Date: Tue, 1 Dec 2009 08:51:22 +1000
From: "Ross McKinnon" <[email protected]>
Subject: Our new silverlight site
To: <[email protected]>
Message-ID:
        <b831d8c1e208ef4eb6649bb8fff94f3607db0...@aumail.michaelhill.global>
Content-Type: text/plain; charset="us-ascii"

Hi all, as you guys aren't exactly our target market, this can't be
considered a cheap marketing email to promote our new website, but more
a demonstration of how silverlight can be utilized to create a global
retail branding site.

On Monday, we released our new website which is written completely in
silverlight. If you get a chance to look at the site
(www.michaelhill.com) it has a number of interesting technical features
that I would like to point out to you all.

1.      Heavy integration of smooth streaming video.
2.      Deep zoom for the product carousel.  Significant bandwidth
savings are made by the in-built lazy loading of deep zoom product
images, plus the natural friction effect.
3.      Integrated video inside a deep zoom image  (company history
section).
4.      Search engine optimisation.
5.      Deep linking :
a.      From search engine optimisation links
b.      Send to friend links
c.      Browser integration with forward/back buttons
d.      Sets the browser/tab title
e.      Appropriate link / title for adding to browser favourites.
6.      Client side state.  This reduces load on server such that when a
user visits a page once, then navigates away / back, the application
doesn't have to fetch data from the server.  This is difficult to do in
a traditional web application.
7.      Custom install experience.
8.      Analytics integration (via google analytics / javascript).
9.      Isolated storage allows us to persist a 'super cookie' using
serialized C# objects.
10.     MVVM pattern.  Dependency injection.
11.     Application lifetime objects / client side services.
12.     Animations / effects / scaling create smoother experience for
user without unsightly page refreshes.
13.     ADO.NET data services integration.  Rest based / loosely coupled
/ dynamic data access.
a.      Easy to secure via policies rather than code.
14.     Data driven application, where all menus / and content on
particular screens can be changed via CMS.  For example, the product
carousels are all data driven.  Dynamic loading of Xaml at runtime
allows us to substitute in content / animations without rebuilding the
application.

You might have seen Ross Jempson post to the silverlight list
occasionally. He is the owner and primary developer of the development
company that implemented our site. We believe we have achieved a
fantastic result and the capability of silverlight has helped us get
there.

Enjoy,

Ross (on day 1.....)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://prdlxvm0001.codify.net/pipermail/ozsilverlight/attachments/20091201/9e7f3728/attachment-0001.html

------------------------------

Message: 4
Date: Mon, 30 Nov 2009 18:54:43 -0500
From: Nick Randolph <[email protected]>
Subject: RE: Our new silverlight site
To: ozSilverlight <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Ross

Since as you said this was a bit of a "cheap marketing email" I'm going to 
retaliate by providing what I hope will be constructive criticism:


-          I hate menus that disappear! The way the menus disappear completely 
makes the site hard to use.  I flipped windows whilst the site was loading 
(sorry short attention span) and when I came back the menus had already gone - 
took me a while to find them.

-          The site's infuriatingly slow - all the ui transitions are too slow 
for my liking.

-          There are some positioning issues whereby the close icon is half cut 
off by the edge of the screen

-          When you go into looking at one of the products 
(http://www.michaelhill.com/#ProductList?ProductMenuItemId=8&ProductMenuSubItemId=&ParentScreenId=3)
 it's then not clear where to go from there.....

General feedback - visually it's quite pleasing. Navigation leaves quite a bit 
to be desired.

Nick Randolph | Built To Roam | Microsoft MVP - Device Application Development 
| +61 412 413 425
The information contained in this email is confidential. If you are not the 
intended recipient, you may not disclose or use the information in this email 
in any way. Built To Roam does not guarantee the integrity of any emails or 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Built To Roam.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Ross McKinnon
Sent: Tuesday, 1 December 2009 9:51 AM
To: [email protected]
Subject: Our new silverlight site


Hi all, as you guys aren't exactly our target market, this can't be considered 
a cheap marketing email to promote our new website, but more a demonstration of 
how silverlight can be utilized to create a global retail branding site.



On Monday, we released our new website which is written completely in 
silverlight. If you get a chance to look at the site 
(www.michaelhill.com<http://www.michaelhill.com>) it has a number of 
interesting technical features that I would like to point out to you all.

1.      Heavy integration of smooth streaming video.

2.      Deep zoom for the product carousel.  Significant bandwidth savings are 
made by the in-built lazy loading of deep zoom product images, plus the natural 
friction effect.

3.      Integrated video inside a deep zoom image  (company history section).

4.      Search engine optimisation.

5.      Deep linking :

a.      From search engine optimisation links

b.      Send to friend links

c.      Browser integration with forward/back buttons

d.      Sets the browser/tab title

e.      Appropriate link / title for adding to browser favourites.

6.      Client side state.  This reduces load on server such that when a user 
visits a page once, then navigates away / back, the application doesn't have to 
fetch data from the server.  This is difficult to do in a traditional web 
application.

7.      Custom install experience.

8.      Analytics integration (via google analytics / javascript).

9.      Isolated storage allows us to persist a 'super cookie' using serialized 
C# objects.

10.     MVVM pattern.  Dependency injection.

11.     Application lifetime objects / client side services.

12.     Animations / effects / scaling create smoother experience for user 
without unsightly page refreshes.

13.     ADO.NET data services integration.  Rest based / loosely coupled / 
dynamic data access.

a.      Easy to secure via policies rather than code.

14.     Data driven application, where all menus / and content on particular 
screens can be changed via CMS.  For example, the product carousels are all 
data driven.  Dynamic loading of Xaml at runtime allows us to substitute in 
content / animations without rebuilding the application.

You might have seen Ross Jempson post to the silverlight list occasionally. He 
is the owner and primary developer of the development company that implemented 
our site. We believe we have achieved a fantastic result and the capability of 
silverlight has helped us get there.

Enjoy,

Ross (on day 1.....)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://prdlxvm0001.codify.net/pipermail/ozsilverlight/attachments/20091130/418035ac/attachment.html

------------------------------

_______________________________________________
ozsilverlight mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight


End of ozsilverlight Digest, Vol 4, Issue 1
*******************************************

Note:  The information contained in this message and any attachment to it is 
privileged, confidential and protected from disclosure.  If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution or copying of this communication is strictly 
prohibited.  If you have received this communication in error, please notify 
the sender immediately by replying to the message, and please delete it from 
your system.  Thank you.  Cynergy Systems.

_______________________________________________
ozsilverlight mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

Reply via email to