Hi Eric, Just wondering if there is any update on this issue? I know you said you kicked off a dialog with your core team but is it possible for you to tell us if this issue is something that will be fixed soon or we have to wait for the next api release?
Please let us know. Thanks. Tejesh. On Jan 20, 2:22 pm, codeninja <shettytej...@gmail.com> wrote: > Thanks for the update. > > On Jan 20, 1:57 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > > > Hi, > > > I'm also seeing the 200 status code for faults, which doesn't appear > > correct. I've opened a dialog with the core engineering team, and > > I'll let you know when I have more information. > > > Best, > > - Eric Koleda, AdWords API Team > > > On Jan 19, 3:14 pm, codeninja <shettytej...@gmail.com> wrote: > > > > With new 2009 api I get http status code of 200 for soap faults. Is > > > this something that was changed in 2009 api intentionally or should it > > > be 500 like v13? > > > > I am using spring webservices to make soap calls, and because of soap > > > spec, it expects all soap faults to have http status code of 500. > > > Since response comes back with 200 it thinks that it is not a soap > > > fault but then during regular unmarshalling the code barfs. I am > > > testing all this with CampaignService and trying to update campaign > > > budget with 0 value and thats when adwords is throwing soap fault with > > > http response code of 200. > > > > Anyone else seeing this? -- 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-...@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.
