Thanks for reporting your findings Koen. UrlFetchTransport is still supposed to be the recommended choice on Google App Engine. There is a flaw in Google App Engine implementation of HttpURLConnection in terms of parsing HTTP headers, whereas UrlFetch doesn't have that flaw. But if NetHttpTransport is working for you, then you may continue to use it.
However, honestly I have not tried it with App Engine 1.6.6. I have only tried it on 1.6.5. I'd really like to see an investigation of what causes it to fail on 1.6.6. Another possibility is that it is not new to 1.6.6, but rather something different about the way you set up your environment. -- Yaniv On Tuesday, May 29, 2012 4:47:53 PM UTC-4, Koen Maes wrote: > > I got confirmation from another user in the google-api-java-client group. > The workaround is to drop UrlFetchTransport and use NetHttpTransport which > seems to be supported nowadays on AppEngine. > > see here : > https://groups.google.com/forum/?fromgroups#!topic/google-api-java-client/FJSsz5qo7pg > > My app is working in production now. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/C2jQtkA1xiwJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
