On Sunday, 15 July 2012 04:35:09 UTC+1, Andrew Arnott wrote:
> I've seen a few reports (all recently) on this gzip problem. Although I
> haven't seen it myself. I'd like to understand it better to see if a DNOA
> fix is appropriate, but I either need complete Fiddler logs of the problem,
> or a way to reproduce it myself, I think.
> --
> Andrew Arnott
> "I [may] not agree with what you have to say, but I'll defend to the death
> your right to say it." - S. G. Tallentyre
> On Fri, Jul 13, 2012 at 3:13 AM, TJA <thoma...@hotmail.fr <javascript:>>wrote:
>> Hi again,
>> After some investigation, I noticed that the web server is behind and
>> entreprise proxy that seems to fiddle with my request and responses a
>> little. After chaning the server network connection and bypassing the
>> entreprise proxy, it seems to work as expected.
>> However I have a feeling that the error should not be raised anyway. I
>> compared the raw request/responses in fiddler and the only difference seems
>> to be the presence of the Proxy-Connection: keep-alive and Via tags.
>> What do you think about it ?
>> Thanks,
>> Thomas
>> Le jeudi 12 juillet 2012 18:16:23 UTC+2, TJA a écrit :
>>> Hi guys,
>>> I'm facing some strange problem with twitter authentication that I've
>>> implemented into my web site with DotNetOpenAuth v4.1.0.0. From time to
>>> time I get *System.ArgumentException*
>>> *'gzip' is not a supported encoding name.*
>>> *Parameter name: name*
>>> With the following stacktrace (my code calls excluded) :
>>> at System.Globalization.**EncodingTable.**internalGetCodePageFromName(**String
>>> name)
>>> at System.Globalization.**EncodingTable.**GetCodePageFromName(String
>>> name)
>>> at DotNetOpenAuth.Messaging.**NetworkDirectWebResponse.**
>>> GetResponseReader()
>>> at DotNetOpenAuth.OAuth.**ChannelElements.OAuthChannel.**
>>> ReadFromResponseCore(**IncomingWebResponse response)
>>> at DotNetOpenAuth.Messaging.**Channel.RequestCore(**IDirectedProtocolMessage
>>> request)
>>> at DotNetOpenAuth.Messaging.**Channel.Request(**IDirectedProtocolMessage
>>> requestMessage)
>>> at DotNetOpenAuth.Messaging.**Channel.Request[TResponse](**IDirectedProtocolMe ssage
>>> requestMessage)
>>> at DotNetOpenAuth.OAuth.**ConsumerBase.**ProcessUserAuthorization(**String
>>> requestToken, String verifier)
>>> at DotNetOpenAuth.OAuth.**WebConsumer.**ProcessUserAuthorization(**HttpRequest Base
>>> request)
>>> at DotNetOpenAuth.OAuth.**WebConsumer.**ProcessUserAuthorization()
>>> This happens quite often but not all the time. I can get the exception,
>>> then try to log in again and succed with the login. The line that throws
>>> the exception is :
>>> var response = TwitterSignIn.P**rocessUserAuthorization();
>>> Do you have any idea what's happening ? Maybe you could guide me where I
>>> could find more information on how to resolve it ?
>>> Thanks,
>>> Thomas
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "DotNetOpenAuth" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/dotnetopenid/-/YGJFbpjPYK4J.
>> To post to this group, send email to dotnet...@googlegroups.com<javascript:>
>> .
>> To unsubscribe from this group, send email to
>> dotnetopenid...@googlegroups.com <javascript:>.
>> For more options, visit this group at
>> http://groups.google.com/group/dotnetopenid?hl=en.
