Re: [caldav] Retry request status
Tim Olsen <tim@brooklynpenguin.com> Fri, 12 March 2010 19:17 UTC
Return-Path: <tim@brooklynpenguin.com>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70EE13A6848 for <caldav@core3.amsl.com>; Fri, 12 Mar 2010 11:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2IyDO4OTWb-I for <caldav@core3.amsl.com>; Fri, 12 Mar 2010 11:17:28 -0800 (PST)
Received: from dubstep.brooklynpenguin.com (dubstep.brooklynpenguin.com [216.254.75.249]) by core3.amsl.com (Postfix) with ESMTP id 533D73A676A for <caldav@ietf.org>; Fri, 12 Mar 2010 11:17:28 -0800 (PST)
Received: from nyc01.limewire.com ([38.108.107.34] helo=[10.254.200.116]) by dubstep.brooklynpenguin.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <tim@brooklynpenguin.com>) id 1NqAMT-0000u6-4w; Fri, 12 Mar 2010 19:17:33 +0000
Message-ID: <4B9A933A.80308@brooklynpenguin.com>
Date: Fri, 12 Mar 2010 14:17:14 -0500
From: Tim Olsen <tim@brooklynpenguin.com>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
MIME-Version: 1.0
To: Mike Douglass <douglm@rpi.edu>
References: <4B9A905A.2060804@rpi.edu>
In-Reply-To: <4B9A905A.2060804@rpi.edu>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam_score: -4.0
X-Spam_score_int: -39
X-Spam_bar: ----
X-Spam_report: Spam detection software, running on the system "dubstep.brooklynpenguin.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Mike Douglass wrote: > I'm thinking of a 409 response with an error response like <DAV:retry/> I recommend a 503 with a Retry-After header. See http://www.greenbytes.de/tech/webdav/rfc2616.html#status.503 [...] Content analysis details: (-4.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.4 AWL AWL: From: address is in the auto white-list
Cc: caldav@ietf.org
Subject: Re: [caldav] Retry request status
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 19:17:29 -0000
Mike Douglass wrote: > I'm thinking of a 409 response with an error response like <DAV:retry/> I recommend a 503 with a Retry-After header. See http://www.greenbytes.de/tech/webdav/rfc2616.html#status.503 Tim
- [caldav] Retry request status Mike Douglass
- Re: [caldav] Retry request status Tim Olsen
- Re: [caldav] Retry request status Mike Douglass
- Re: [caldav] Retry request status Cyrus Daboo
- Re: [caldav] Retry request status Mike Douglass