I am using DNOA to authenticate users against Google. I have noticed
that I get the following exceptions logged in the log file even though
the authentication goes on to succeed. I am using version 4.0.0.12084
of DotNetOpenAuth.
The thread you linked to was never fully resolved, although a private build
I prepared for those folks alleviated the symptoms. I'm not sure your
symptoms are the same though -- they don't sound similar yet.
If you can please send me the full log I'd appreciate it. It would be
helpful if you could preserve it exactly (no obfuscated domain names) so
that I can try reproducing it if necessary. Feel free to send it privately
just to me if that's more comfortable.
--
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 Tue, May 1, 2012 at 10:58 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
> I am using DNOA to authenticate users against Google. I have noticed
> that I get the following exceptions logged in the log file even though
> the authentication goes on to succeed. I am using version 4.0.0.12084
> of DotNetOpenAuth.
> I was wondering if this is expected or not?
> This thread seems pretty similar to what I am seeing (i.e. it is slow,
> similar errors and in the end it succeeds) but it is two years old now
> so I am not sure if it still applies:
> https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo... > :
> DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
> sending a direct message or getting the response. --->
> System.Net.WebException: The remote server returned an error: (400)
> Bad Request.
> at System.Net.HttpWebRequest.GetResponse()
> at
> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque st
> request, DirectWebRequestOptions options) in c:\BuildAgent\work
> \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> \StandardWebRequestHandler.cs:line 127
> --- End of inner exception stack trace ---
> at
> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque st
> request, DirectWebRequestOptions options) in c:\BuildAgent\work
> \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> \StandardWebRequestHandler.cs:line 173
> at
> DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ est
> request, DirectWebRequestOptions options) in c:\BuildAgent\work
> \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> \UntrustedWebRequestHandler.cs:line 250
> at
> DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie r
> identifier, IDirectWebRequestHandler requestHandler, Uri xrdsLocation)
> in c:\BuildAgent\work\6fe1ab573d75f9ba\src
> \DotNetOpenAuth.OpenId.RelyingParty\OpenId
> \HostMetaDiscoveryService.cs:line 311
> at
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
> The thread you linked to was never fully resolved, although a private build
> I prepared for those folks alleviated the symptoms. I'm not sure your
> symptoms are the same though -- they don't sound similar yet.
> If you can please send me the full log I'd appreciate it. It would be
> helpful if you could preserve it exactly (no obfuscated domain names) so
> that I can try reproducing it if necessary. Feel free to send it privately
> just to me if that's more comfortable.
> --
> 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 Tue, May 1, 2012 at 10:58 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
> > Hello
> > I am using DNOA to authenticate users against Google. I have noticed
> > that I get the following exceptions logged in the log file even though
> > the authentication goes on to succeed. I am using version 4.0.0.12084
> > of DotNetOpenAuth.
> > I was wondering if this is expected or not?
> > This thread seems pretty similar to what I am seeing (i.e. it is slow,
> > similar errors and in the end it succeeds) but it is two years old now
> > so I am not sure if it still applies:
> >https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo...
> > :
> > DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
> > sending a direct message or getting the response. --->
> > System.Net.WebException: The remote server returned an error: (400)
> > Bad Request.
> > at System.Net.HttpWebRequest.GetResponse()
> > at
> > DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque st
> > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > \StandardWebRequestHandler.cs:line 127
> > --- End of inner exception stack trace ---
> > at
> > DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque st
> > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > \StandardWebRequestHandler.cs:line 173
> > at
> > DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ est
> > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > \UntrustedWebRequestHandler.cs:line 250
> > at
> > DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie r
> > identifier, IDirectWebRequestHandler requestHandler, Uri xrdsLocation)
> > in c:\BuildAgent\work\6fe1ab573d75f9ba\src
> > \DotNetOpenAuth.OpenId.RelyingParty\OpenId
> > \HostMetaDiscoveryService.cs:line 311
> > at
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DotNetOpenAuth" group.
> > To post to this group, send email to dotnetopenid@googlegroups.com.
> > To unsubscribe from this group, send email to
> > dotnetopenid+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/dotnetopenid?hl=en.
Yes, I received it. Sorry for the sluggish response. I've skimmed through
the logs and it appears this doesn't show the "perf problem" that I was
investigating a year or so ago. Instead these HTTP 400 error responses
seem like a new issue.
I'm afraid I don't have time to personally investigate why it's failing for
you. Can you contact Google for support?
--
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 Sun, May 6, 2012 at 2:32 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
> I sent the full log file to you last week. I was just wondering if you
> have received it? Thanks very much!
> Cheers,
> Dave
> On May 3, 1:54 am, Andrew Arnott <andrewarn...@gmail.com> wrote:
> > The thread you linked to was never fully resolved, although a private
> build
> > I prepared for those folks alleviated the symptoms. I'm not sure your
> > symptoms are the same though -- they don't sound similar yet.
> > If you can please send me the full log I'd appreciate it. It would be
> > helpful if you could preserve it exactly (no obfuscated domain names) so
> > that I can try reproducing it if necessary. Feel free to send it
> privately
> > just to me if that's more comfortable.
> > --
> > 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 Tue, May 1, 2012 at 10:58 PM, Dave W <dave.whar...@gdev.intilecta.com
> >wrote:
> > > Hello
> > > I am using DNOA to authenticate users against Google. I have noticed
> > > that I get the following exceptions logged in the log file even though
> > > the authentication goes on to succeed. I am using version 4.0.0.12084
> > > of DotNetOpenAuth.
> > > I was wondering if this is expected or not?
> > > This thread seems pretty similar to what I am seeing (i.e. it is slow,
> > > similar errors and in the end it succeeds) but it is two years old now
> > > so I am not sure if it still applies:
> > >https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo.
> ..
> > > :
> > > DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
> > > sending a direct message or getting the response. --->
> > > System.Net.WebException: The remote server returned an error: (400)
> > > Bad Request.
> > > at System.Net.HttpWebRequest.GetResponse()
> > > at
> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
> st
> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > > \StandardWebRequestHandler.cs:line 127
> > > --- End of inner exception stack trace ---
> > > at
> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
> st
> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > > \StandardWebRequestHandler.cs:line 173
> > > at
> DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ
> est
> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
> > > \UntrustedWebRequestHandler.cs:line 250
> > > at
> DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie
> r
> > > identifier, IDirectWebRequestHandler requestHandler, Uri xrdsLocation)
> > > in c:\BuildAgent\work\6fe1ab573d75f9ba\src
> > > \DotNetOpenAuth.OpenId.RelyingParty\OpenId
> > > \HostMetaDiscoveryService.cs:line 311
> > > at
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "DotNetOpenAuth" group.
> > > To post to this group, send email to dotnetopenid@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > dotnetopenid+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/dotnetopenid?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
Yes, I can log this with Google. Do you mind pointing me in the right
direction of where to log this with Google (assuming you might know) and is
it sufficient to say I am getting a 400 (Bad Request) error when accessing
the URL "
https://www.google.com/accounts/o8/user-xrds?uri=http:%2F%2Fsomegoogl..."
via the DNOA library?
Thanks heaps!
Cheers,
Dave
On Fri, May 11, 2012 at 4:04 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
> Yes, I received it. Sorry for the sluggish response. I've skimmed
> through the logs and it appears this doesn't show the "perf problem" that I
> was investigating a year or so ago. Instead these HTTP 400 error responses
> seem like a new issue.
> I'm afraid I don't have time to personally investigate why it's failing
> for you. Can you contact Google for support?
> --
> 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 Sun, May 6, 2012 at 2:32 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
>> Hi Andrew
>> Thanks for your response!
>> I sent the full log file to you last week. I was just wondering if you
>> have received it? Thanks very much!
>> Cheers,
>> Dave
>> On May 3, 1:54 am, Andrew Arnott <andrewarn...@gmail.com> wrote:
>> > The thread you linked to was never fully resolved, although a private
>> build
>> > I prepared for those folks alleviated the symptoms. I'm not sure your
>> > symptoms are the same though -- they don't sound similar yet.
>> > If you can please send me the full log I'd appreciate it. It would be
>> > helpful if you could preserve it exactly (no obfuscated domain names) so
>> > that I can try reproducing it if necessary. Feel free to send it
>> privately
>> > just to me if that's more comfortable.
>> > --
>> > 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 Tue, May 1, 2012 at 10:58 PM, Dave W <
>> dave.whar...@gdev.intilecta.com>wrote:
>> > > Hello
>> > > I am using DNOA to authenticate users against Google. I have noticed
>> > > that I get the following exceptions logged in the log file even though
>> > > the authentication goes on to succeed. I am using version 4.0.0.12084
>> > > of DotNetOpenAuth.
>> > > I was wondering if this is expected or not?
>> > > This thread seems pretty similar to what I am seeing (i.e. it is slow,
>> > > similar errors and in the end it succeeds) but it is two years old now
>> > > so I am not sure if it still applies:
>> > >https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo.
>> ..
>> > > :
>> > > DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
>> > > sending a direct message or getting the response. --->
>> > > System.Net.WebException: The remote server returned an error: (400)
>> > > Bad Request.
>> > > at System.Net.HttpWebRequest.GetResponse()
>> > > at
>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>> st
>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>> > > \StandardWebRequestHandler.cs:line 127
>> > > --- End of inner exception stack trace ---
>> > > at
>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>> st
>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>> > > \StandardWebRequestHandler.cs:line 173
>> > > at
>> DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ
>> est
>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>> > > \UntrustedWebRequestHandler.cs:line 250
>> > > at
>> DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie
>> r
>> > > identifier, IDirectWebRequestHandler requestHandler, Uri xrdsLocation)
>> > > in c:\BuildAgent\work\6fe1ab573d75f9ba\src
>> > > \DotNetOpenAuth.OpenId.RelyingParty\OpenId
>> > > \HostMetaDiscoveryService.cs:line 311
>> > > at
>> > > --
>> > > You received this message because you are subscribed to the Google
>> Groups
>> > > "DotNetOpenAuth" group.
>> > > To post to this group, send email to dotnetopenid@googlegroups.com.
>> > > To unsubscribe from this group, send email to
>> > > dotnetopenid+unsubscribe@googlegroups.com.
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/dotnetopenid?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DotNetOpenAuth" group.
>> To post to this group, send email to dotnetopenid@googlegroups.com.
>> To unsubscribe from this group, send email to
>> dotnetopenid+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/dotnetopenid?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
I don't know of the appropriate place to log this with Google. You'll have
to look through their support system.
I recommend you capture a network trace (using Fiddler perhaps) of the
actual request including all HTTP headers and the error response so Google
can easily reproduce it without using DNOA.
--
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
dave.whar...@gdev.intilecta.com> wrote:
> Hi Andrew
> Thanks for your time looking into this for me.
> Yes, I can log this with Google. Do you mind pointing me in the right
> direction of where to log this with Google (assuming you might know) and is
> it sufficient to say I am getting a 400 (Bad Request) error when accessing
> the URL "
> https://www.google.com/accounts/o8/user-xrds?uri=http:%2F%2Fsomegoogl..."
> via the DNOA library?
> Thanks heaps!
> Cheers,
> Dave
> On Fri, May 11, 2012 at 4:04 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
>> Yes, I received it. Sorry for the sluggish response. I've skimmed
>> through the logs and it appears this doesn't show the "perf problem" that I
>> was investigating a year or so ago. Instead these HTTP 400 error responses
>> seem like a new issue.
>> I'm afraid I don't have time to personally investigate why it's failing
>> for you. Can you contact Google for support?
>> --
>> 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 Sun, May 6, 2012 at 2:32 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
>>> Hi Andrew
>>> Thanks for your response!
>>> I sent the full log file to you last week. I was just wondering if you
>>> have received it? Thanks very much!
>>> Cheers,
>>> Dave
>>> On May 3, 1:54 am, Andrew Arnott <andrewarn...@gmail.com> wrote:
>>> > The thread you linked to was never fully resolved, although a private
>>> build
>>> > I prepared for those folks alleviated the symptoms. I'm not sure your
>>> > symptoms are the same though -- they don't sound similar yet.
>>> > If you can please send me the full log I'd appreciate it. It would be
>>> > helpful if you could preserve it exactly (no obfuscated domain names)
>>> so
>>> > that I can try reproducing it if necessary. Feel free to send it
>>> privately
>>> > just to me if that's more comfortable.
>>> > --
>>> > 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 Tue, May 1, 2012 at 10:58 PM, Dave W <
>>> dave.whar...@gdev.intilecta.com>wrote:
>>> > > Hello
>>> > > I am using DNOA to authenticate users against Google. I have noticed
>>> > > that I get the following exceptions logged in the log file even
>>> though
>>> > > the authentication goes on to succeed. I am using version 4.0.0.12084
>>> > > of DotNetOpenAuth.
>>> > > I was wondering if this is expected or not?
>>> > > This thread seems pretty similar to what I am seeing (i.e. it is
>>> slow,
>>> > > similar errors and in the end it succeeds) but it is two years old
>>> now
>>> > > so I am not sure if it still applies:
>>> > > The exceptions from the logs (I can provide I full log if required):
>>> > > ERROR 2012-05-02 17:00:15,674 7536ms Http
>>> -
>>> > > WebException from
>>> https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo...
>>> > > :
>>> > > DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
>>> > > sending a direct message or getting the response. --->
>>> > > System.Net.WebException: The remote server returned an error: (400)
>>> > > Bad Request.
>>> > > at System.Net.HttpWebRequest.GetResponse()
>>> > > at
>>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>>> st
>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>> > > \StandardWebRequestHandler.cs:line 127
>>> > > --- End of inner exception stack trace ---
>>> > > at
>>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>>> st
>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>> > > \StandardWebRequestHandler.cs:line 173
>>> > > at
>>> DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ
>>> est
>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>> > > \UntrustedWebRequestHandler.cs:line 250
>>> > > at
>>> DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie
>>> r
>>> > > identifier, IDirectWebRequestHandler requestHandler, Uri
>>> xrdsLocation)
>>> > > in c:\BuildAgent\work\6fe1ab573d75f9ba\src
>>> > > \DotNetOpenAuth.OpenId.RelyingParty\OpenId
>>> > > \HostMetaDiscoveryService.cs:line 311
>>> > > at
>>> > > --
>>> > > You received this message because you are subscribed to the Google
>>> Groups
>>> > > "DotNetOpenAuth" group.
>>> > > To post to this group, send email to dotnetopenid@googlegroups.com.
>>> > > To unsubscribe from this group, send email to
>>> > > dotnetopenid+unsubscribe@googlegroups.com.
>>> > > For more options, visit this group at
>>> > >http://groups.google.com/group/dotnetopenid?hl=en.
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "DotNetOpenAuth" group.
>>> To post to this group, send email to dotnetopenid@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> dotnetopenid+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/dotnetopenid?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DotNetOpenAuth" group.
>> To post to this group, send email to dotnetopenid@googlegroups.com.
>> To unsubscribe from this group, send email to
>> dotnetopenid+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/dotnetopenid?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
I know it has been a while since I last asked about this, but I just
noticed trying different versions of DNOA (looking at something totally
different) that I didn't get this error when using version 4.1.2 and 4.1.3,
but I do get it in 4.1.0 and 4.1.4.
Is there something that has changed in 4.1.4 that could have resulted in
seeing this error again? It could be that it is still an issue with Google
of course and 4.1.2 was not calling something it should be etc., but I
thought I would ask out of curiosity.
Thanks again!
Cheers,
Dave
On 17 May 2012 11:52, Andrew Arnott <andrewarn...@gmail.com> wrote:
> I don't know of the appropriate place to log this with Google. You'll
> have to look through their support system.
> I recommend you capture a network trace (using Fiddler perhaps) of the
> actual request including all HTTP headers and the error response so Google
> can easily reproduce it without using DNOA.
> --
> 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 Wed, May 16, 2012 at 3:43 PM, Dave Wharton <
> dave.whar...@gdev.intilecta.com> wrote:
>> Hi Andrew
>> Thanks for your time looking into this for me.
>> Yes, I can log this with Google. Do you mind pointing me in the right
>> direction of where to log this with Google (assuming you might know) and is
>> it sufficient to say I am getting a 400 (Bad Request) error when accessing
>> the URL "
>> https://www.google.com/accounts/o8/user-xrds?uri=http:%2F%2Fsomegoogl..."
>> via the DNOA library?
>> Thanks heaps!
>> Cheers,
>> Dave
>> On Fri, May 11, 2012 at 4:04 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
>>> Yes, I received it. Sorry for the sluggish response. I've skimmed
>>> through the logs and it appears this doesn't show the "perf problem" that I
>>> was investigating a year or so ago. Instead these HTTP 400 error responses
>>> seem like a new issue.
>>> I'm afraid I don't have time to personally investigate why it's failing
>>> for you. Can you contact Google for support?
>>> --
>>> 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 Sun, May 6, 2012 at 2:32 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
>>>> Hi Andrew
>>>> Thanks for your response!
>>>> I sent the full log file to you last week. I was just wondering if you
>>>> have received it? Thanks very much!
>>>> Cheers,
>>>> Dave
>>>> On May 3, 1:54 am, Andrew Arnott <andrewarn...@gmail.com> wrote:
>>>> > The thread you linked to was never fully resolved, although a private
>>>> build
>>>> > I prepared for those folks alleviated the symptoms. I'm not sure your
>>>> > symptoms are the same though -- they don't sound similar yet.
>>>> > If you can please send me the full log I'd appreciate it. It would be
>>>> > helpful if you could preserve it exactly (no obfuscated domain names)
>>>> so
>>>> > that I can try reproducing it if necessary. Feel free to send it
>>>> privately
>>>> > just to me if that's more comfortable.
>>>> > --
>>>> > 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 Tue, May 1, 2012 at 10:58 PM, Dave W <
>>>> dave.whar...@gdev.intilecta.com>wrote:
>>>> > > Hello
>>>> > > I am using DNOA to authenticate users against Google. I have noticed
>>>> > > that I get the following exceptions logged in the log file even
>>>> though
>>>> > > the authentication goes on to succeed. I am using version
>>>> 4.0.0.12084
>>>> > > of DotNetOpenAuth.
>>>> > > I was wondering if this is expected or not?
>>>> > > This thread seems pretty similar to what I am seeing (i.e. it is
>>>> slow,
>>>> > > similar errors and in the end it succeeds) but it is two years old
>>>> now
>>>> > > so I am not sure if it still applies:
>>>> > > The exceptions from the logs (I can provide I full log if required):
>>>> > > ERROR 2012-05-02 17:00:15,674 7536ms Http
>>>> -
>>>> > > WebException from
>>>> https://www.google.com/accounts/o8/user-xrds?uri=http%3A%2F%2Fsomegoo.
>>>> ..
>>>> > > :
>>>> > > DotNetOpenAuth.Messaging.ProtocolException: Error occurred while
>>>> > > sending a direct message or getting the response. --->
>>>> > > System.Net.WebException: The remote server returned an error: (400)
>>>> > > Bad Request.
>>>> > > at System.Net.HttpWebRequest.GetResponse()
>>>> > > at
>>>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>>>> st
>>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>>> > > \StandardWebRequestHandler.cs:line 127
>>>> > > --- End of inner exception stack trace ---
>>>> > > at
>>>> DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebReque
>>>> st
>>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>>> > > \StandardWebRequestHandler.cs:line 173
>>>> > > at
>>>> DotNetOpenAuth.Messaging.UntrustedWebRequestHandler.GetResponse(HttpWebRequ
>>>> est
>>>> > > request, DirectWebRequestOptions options) in c:\BuildAgent\work
>>>> > > \6fe1ab573d75f9ba\src\DotNetOpenAuth.Core\Messaging
>>>> > > \UntrustedWebRequestHandler.cs:line 250
>>>> > > at
>>>> DotNetOpenAuth.OpenId.HostMetaDiscoveryService.GetXrdsResponse(UriIdentifie
>>>> r
>>>> > > identifier, IDirectWebRequestHandler requestHandler, Uri
>>>> xrdsLocation)
>>>> > > in c:\BuildAgent\work\6fe1ab573d75f9ba\src
>>>> > > \DotNetOpenAuth.OpenId.RelyingParty\OpenId
>>>> > > \HostMetaDiscoveryService.cs:line 311
>>>> > > at
>>>> > > --
>>>> > > You received this message because you are subscribed to the Google
>>>> Groups
>>>> > > "DotNetOpenAuth" group.
>>>> > > To post to this group, send email to dotnetopenid@googlegroups.com.
>>>> > > To unsubscribe from this group, send email to
>>>> > > dotnetopenid+unsubscribe@googlegroups.com.
>>>> > > For more options, visit this group at
>>>> > >http://groups.google.com/group/dotnetopenid?hl=en.
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "DotNetOpenAuth" group.
>>>> To post to this group, send email to dotnetopenid@googlegroups.com.
>>>> To unsubscribe from this group, send email to
>>>> dotnetopenid+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/dotnetopenid?hl=en.
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "DotNetOpenAuth" group.
>>> To post to this group, send email to dotnetopenid@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> dotnetopenid+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/dotnetopenid?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DotNetOpenAuth" group.
>> To post to this group, send email to dotnetopenid@googlegroups.com.
>> To unsubscribe from this group, send email to
>> dotnetopenid+unsubscribe@googlegroups.com.
>> For
I can’t think of any reason 4.1.4 would have regressed this behavior off
hand.
*From:* Dave Wharton <dave.whar...@gdev.intilecta.com>
*Sent:* January 9, 2013 5:21 PM
*To:* DotNetOpenAuth <dotnetopenid@googlegroups.com>
*Subject:* Re: [dotnetopenauth] Re: Bad Request Exception when calling
CreateRequest against Google
Hi Andrew
I know it has been a while since I last asked about this, but I just
noticed trying different versions of DNOA (looking at something totally
different) that I didn't get this error when using version 4.1.2 and 4.1.3,
but I do get it in 4.1.0 and 4.1.4.
Is there something that has changed in 4.1.4 that could have resulted in
seeing this error again? It could be that it is still an issue with Google
of course and 4.1.2 was not calling something it should be etc., but I
thought I would ask out of curiosity.
Thanks again!
Cheers,
Dave
On 17 May 2012 11:52, Andrew Arnott <andrewarn...@gmail.com> wrote:
I don't know of the appropriate place to log this with Google. You'll have
to look through their support system.
I recommend you capture a network trace (using Fiddler perhaps) of the
actual request including all HTTP headers and the error response so Google
can easily reproduce it without using DNOA.
--
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, May 11, 2012 at 4:04 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
Yes, I received it. Sorry for the sluggish response. I've skimmed through
the logs and it appears this doesn't show the "perf problem" that I was
investigating a year or so ago. Instead these HTTP 400 error responses
seem like a new issue.
I'm afraid I don't have time to personally investigate why it's failing for
you. Can you contact Google for support?
--
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 Sun, May 6, 2012 at 2:32 PM, Dave W <dave.whar...@gdev.intilecta.com>wrote:
Hi Andrew
Thanks for your response!
I sent the full log file to you last week. I was just wondering if you
have received it? Thanks very much!
Cheers,
Dave
On May 3, 1:54 am, Andrew Arnott <andrewarn...@gmail.com> wrote:
> The thread you linked to was never fully resolved, although a private
build
> I prepared for those folks alleviated the symptoms. I'm not sure your
> symptoms are the same though -- they don't sound similar yet.
> If you can please send me the full log I'd appreciate it. It would be
> helpful if you could preserve it exactly (no obfuscated domain names) so
> that I can try reproducing it if necessary. Feel free to send it
privately
> just to me if that's more comfortable.
> --
> 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 Tue, May 1, 2012 at 10:58 PM, Dave W <dave.whar...@gdev.intilecta.com
>wrote:
> > Hello
> > I am using DNOA to authenticate users against Google. I have noticed
> > that I get the following exceptions logged in the log file even though
> > the authentication goes on to succeed. I am using version 4.0.0.12084
> > of DotNetOpenAuth.
> > I was wondering if this is expected or not?
> > This thread seems pretty similar to what I am seeing (i.e. it is slow,
> > similar errors and in the end it succeeds) but it is two years old now
> > so I am not sure if it still applies:
> > --
> > You received this message because you are subscribed to the Google
Groups
> > "DotNetOpenAuth" group.
> > To post to this group, send email to dotnetopenid@googlegroups.com.
> > To unsubscribe from this group, send email to
> > dotnetopenid+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/dotnetopenid?hl=en.
--
You received this message because you are subscribed to the Google Groups
"DotNetOpenAuth" group.
To post to this group, send email to dotnetopenid@googlegroups.com.
To unsubscribe from this group, send email to
dotnetopenid+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/dotnetopenid?hl=en.
-- You received this message because you are subscribed to the Google Groups
"DotNetOpenAuth" group.
To post to this group, send email to dotnetopenid@googlegroups.com.
To unsubscribe from this group, send email to
dotnetopenid+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/dotnetopenid?hl=en.
-- You received this message because you are subscribed to the Google Groups
"DotNetOpenAuth" group.
To post to this group, send email to dotnetopenid@googlegroups.com.
To unsubscribe from this group, send email to
dotnetopenid+unsubscribe@googlegroups.com.
For more options, visit this group at
...