On Wed, Oct 22, 2008 at 9:44 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Clif and I emailed back and forth and figured this out. I'm going to > post the answer here in case the solution helps someone else. > > The issue appears to be a bug in the way that cfhttp handles 302 > redirects when using the PUT method. By default, cfhttp follows the > redirect, but changes the method to GET, and drops the xml from the > body - it's similar to the way that most browsers respond to a > redirect when using the POST method. > > Anyway, the fix it to use the redirect attribute to tell cfhttp to not > follow redirects, and then to manually handle them in your code
Ah, I'm glad you guys got it figured out. I couldn't find anything obvoiusly wrong with the code snippet you had posted. We actually ran into a similar problem with our Python client library on App Engine about a month ago, and came up with a similar solution. :) -- Trevor Johns --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
