Hello Kyle, thank you for your answer. > I'm not sure it's the source of your problem, but providing the > Content-Type header on a delete is odd because there really is no > content. It should be ignored because the Content-Length header is > zero, but maybe there is a subtle bug here. The Content-Type header > value for PUT must be "application/atom+xml" to reflect the Atom entry > payload of the request.
On the direct DELETE request I didn't have a content type. Since I found a line in the java client api readme telling me that there is a known issue, I used POST and X-HTTP-Method-Override. If I submit a POST request, I need a content type and a content length. Otherwise I recieved a "Content Length required" with an appropriate HTTP error code. I use a valid content type with a PUT request. About the optimistic concurrency, I have read this before but I stopped when I read "The implementation of this approach to optimistic concurrency is optional." (Found at the url you posted) thinking I could implement this when everything else works. I just used a generic url as my edit url. The generic format I used is 'http://www.google.com/feeds/' + mCalendarName + '/private/full/ + aItemID If I get the item using this URL, it does indeed contain an edit URL, but if optimistic concurrency is optional, I should be able to delete the item without using the edit url. Is it now required to use optimistic concurrency? If so, you/google should update the documentation to reflect this. > Also, are you able to successfully GET using this entry URL and the > auth key? Is there any http error response body sent back along > with the 400 error response below? Oh yes, I'm sorry. I thought I added the error text. I get "Invalid request URI.". I am able to GET the url fine and recieve the event in XML form. > Re: the "close" header, believe it or not this is by design. This is > actually an expected behavior related to HTTP Keep-Alive handling. I know it is, but take a close look at the spelling of the header key (Cneonction). The correct spelling is of course "Connection". I know that Connection: close is a valid header. Update: I was able to delete an event with lwp-request using the edit url without problems, using the DELETE method directly and also with POST and X-HTTP-Method-Override. This lets me assume that optimistic concurrency is required. Please update the documentation on this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
