Skip to content
This repository has been archived by the owner on Dec 28, 2022. It is now read-only.

409 Conflict Handling is broken #35

Closed
GoogleCodeExporter opened this issue Sep 6, 2015 · 1 comment
Closed

409 Conflict Handling is broken #35

GoogleCodeExporter opened this issue Sep 6, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Type: Defect
Server: Calendar

What steps will reproduce the problem?
1. Create an Event, note the sequence number
2. Modify the event
3. Delete or modify the event using the old sequence number

What is the expected output? What do you see instead?
* A 409 Conflict with the new version of the event is expected
* Instead, on a delete, a 200 OK is recieved and the event is deleted
* Instead, on a modification, a 400 Bad Request with the body
  "Sequence ids from event: <id before> and <id after> do not match."

Please provide any additional information below.
The following threads are related:
http://groups-beta.google.com/group/google-calendar-help-dataapi/browse_thread/t
hread/5a091ab0ef943cd
http://groups-beta.google.com/group/google-calendar-help-dataapi/browse_thread/t
hread/baf988e8cc953e2

Original issue reported on code.google.com by kewi...@gmail.com on 16 Dec 2006 at 3:25

@GoogleCodeExporter
Copy link
Author

This is now functioning properly.  The response for step 3 is a 409 Conflict 
with a
body containing the current representation of the event on the calendar server.

Original comment by api.rb...@gmail.com on 25 Jan 2007 at 7:41

  • Changed state: Fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant