The "protocol violation" with the misleading error message

Before reading this, refresh your memory of Joel Spolsky's wonderful post on the Law of Leaky Abstractions [http://www.joelonsoftware.com/articles/LeakyAbstractions.html]. After determining it was possible to write a replacement HttpClient for WP8.1 Silverlight [https://www.

Dealing with a "protocol violation" on WP 8.1

In my last post [https://www.jedidja.ca/wp8-debugging-for-fun-and-profit/], I discussed how Windows Phone and Store apps will refuse to parse HTTP responses (namely headers) that do not strictly follow RFC2616 [http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4]

WP8 Debugging for Fun and ... Profit?

Since I lost several hours on this today, I thought I'd quickly share my experience. There were very few results for the inital terms I searched for so perhaps this may help someone in the future. Laziness I've been working

Close You've successfully subscribed to jedidja.ca.
Close Great! You've successfully signed up.
Close Welcome back! You've successfully signed in.
Close Success! Your account is fully activated, you now have access to all content.
Close Success! Your billing info is updated.
Close Billing info update failed.