Hello Reed,

 That's new to me as well. If for some reason our public-facing HTTP
servers can't pass your SOAP request along to our AdWords API servers,
you would normally get back a 502/503 HTTP response code, not a 200.
And I'm not sure what other possible "Connection Failure" might take
place.

 So... I'm not sure. Is anyone else seeing similar behavior?

Cheers,
-Jeff Posnick, AdWords API Team


On Apr 28, 5:08 pm, Reed <pow...@nauticom.net> wrote:
> From time to time I've been getting weird parsing errors in XML
> returned from the adWords API.  Today I found the following:  I sent a
> getAllAds request to the adService, and got back an HTTP status of
> 200, but the HTTP response content contained nothing but the words
> "Connection Failure" instead of the usual XML document.
>
> There have been other times when I've received the "Connection
> Failure" as the actual HTTP status code, but this seems pretty strange
> that it would be in the body of the message that came back with a 200
> status code. I'm running on Java/Axis, and would figure that if I got
> the 200 status then the GET to the adWords API at least got out of my
> server and to the adWords server, so I don't think that the problem is
> in something that Axis is doing.
>
> There's no easy way to reproduce this, sometimes it happens &
> sometimes it doesn't, but since I probably do thousands of calls to
> the API every night, it's bound to happen more often than I'd like.
>
> Is there logic behind this behavior that I'm not aware of?  I don't
> recall ever seeing mention of this before.
>
> thanks
> -reed
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to