- From: <jose.kahan@w3.org>
- Date: Thu, 23 Dec 1999 23:05:14 +0100 (MET)
- To: kotok@w3.org (Alan Kotok)
- Cc: www-amaya@w3.org, yves@w3.org
Hello Alan, Thanks for your report. I've seen this problem and I now know what it is. The problem comes from redirecting the PUT from one server to another. The lost updates protection works fine, but not in this case. Jigedit and Apache use different etag values. When you PUT, Jigedit returns a new etag value. But, as far as libwww knows, the etag on www.w3.org hasn't changed at all. Then, the next time you publish, libwww requests "PUT this document only if the etag hasn't changed", but of course the etag has changed in the meantime because the document has changed too. Next month, I'll make a better analysis and brainstorm if needed with Yves and DLL to see how best to solve it. -Jose In our previous episode, Alan Kotok said: > > Publishing prefs set to allow automatic redirection of puts to www.w3.org.
Received on Thursday, 23 December 1999 17:05:23 UTC