[CalendarServer-changes] [3666] CalendarServer/trunk

[source_changes at macosforge.org]

Revision: 3666
          http://trac.macosforge.org/projects/calendarserver/changeset/3666
Author:   wsanchez at apple.com
Date:     2009-02-12 15:16:37 -0800 (Thu, 12 Feb 2009)
Log Message:
-----------
Let's not support RetryAfter as an HTTP-date in the config; don't see a use case for it.

Modified Paths:
--------------
    CalendarServer/trunk/conf/caldavd-test.plist
    CalendarServer/trunk/twistedcaldav/config.py

Modified: CalendarServer/trunk/conf/caldavd-test.plist
===================================================================
--- CalendarServer/trunk/conf/caldavd-test.plist	2009-02-12 23:15:54 UTC (rev 3665)
+++ CalendarServer/trunk/conf/caldavd-test.plist	2009-02-12 23:16:37 UTC (rev 3666)
@@ -615,9 +615,7 @@
     <key>ResponseCompression</key>
     <false/>
     
-    <!-- The retry-after value to return with a 503 error.  The value of this field can be either
-         an integer number of seconds (e.g. 180) or an HTTP-date 
-         (e.g. Sat, 14 Feb 2009 23:59:59 GMT). -->
+    <!-- The retry-after value (in seconds) to return with a 503 error. -->
     <key>HTTPRetryAfter</key>
     <string>180</string>
 

Modified: CalendarServer/trunk/twistedcaldav/config.py
===================================================================
--- CalendarServer/trunk/twistedcaldav/config.py	2009-02-12 23:15:54 UTC (rev 3665)
+++ CalendarServer/trunk/twistedcaldav/config.py	2009-02-12 23:16:37 UTC (rev 3666)
@@ -386,10 +386,8 @@
     # RFC2616 Section 3.5
     "ResponseCompression": True,
 
-    # The retry-after value to return with a 503 error
-    # Can be either a duration (in seconds) or a specific time (e.g.
-    # Fri, 31 Dec 1999 23:59:59 GMT
-    "HTTPRetryAfter": "180",
+    # The retry-after value (in seconds) to return with a 503 error
+    "HTTPRetryAfter": 180,
 
     # Profiling options
     "Profiling": {
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20090212/d8d3d8af/attachment-0001.html>