Community
Participate
Working Groups
We need to detect the case where a PUT is based on a revision of the resource that doesn't match the current server contetents. I.e., use ETag and If-Modified-Since headers to cause PUT to fail if not based on
Tomek we already have separate bugs for using ETag for commit and push operations, right?
(In reply to comment #1) > we already have separate bugs for using ETag for commit and push Yup, for git these are: bug 339848, bug 338121, bug 338122 and bug 339846.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html