Open GoogleCodeExporter opened 9 years ago
Ah, forgot: as mentioned in Issue 12 it would be best if Google would work
around the
whole issue by storing the URL choosen by the client in the event/contact
record.
It needs to track an additional unique ID (in addition to the iCal UID), but it
would
be much bette for WebDAV interoperability.
Original comment by helge.h...@googlemail.com
on 11 Aug 2008 at 8:32
Todays deployment returns a Location header with status 201 after a PUT.
So I suppose we can close this issue.
Original comment by helge.h...@googlemail.com
on 5 Oct 2008 at 11:20
And it's broken again. After recent update on Google's CalDAV side (I cannot
think of any other change) the Location header is not returned, thus the client
doesn't know where just added event came. This is a regression from previous
behaviour and breaks 3rd party clients which depend on the Location header.
Could you refix this, please?
Original comment by milan.c...@gmail.com
on 16 Apr 2012 at 5:50
Original issue reported on code.google.com by
helge.h...@googlemail.com
on 11 Aug 2008 at 8:29