mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-03-14 08:10:13 +00:00
c5c97ad5d2
It seems that on PUT Google might truncate the filename, so it will send us back a Location header we need to follow before we can getr the ETag. And there might be one more hoop to jump through to complete this process. This would be better handled if we locally use the VEVENT UID as the invariant property between local and remote, rather than the 'filename' part of the path, but we'd still face the issue of having to follow the Location: header to get the ETag for the event we just PUT to the remote server.
DAViCal CalDAV Server by Andrew McMillan. For documentation you are best advised to visit the sourceforge pages or to start searching from http://davical.org/ and see where you end up. Good luck! Andrew McMillan ----------------------------------------------- Copyright: 2006-2008 Andrew McMillan <andrew@catalyst.net.nz> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA