[Mono-bugs] [Bug 77826][Nor] Changed - [PATCH] SetCacheability(HttpCacheability.Server) generates "Expires" header

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Mar 21 12:50:07 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo at ximian.com.


--- shadow/77826	2006-03-18 20:08:43.000000000 -0500
+++ shadow/77826.tmp.17285	2006-03-21 12:50:07.000000000 -0500
@@ -5,13 +5,13 @@
 OS Details: 
 Status: NEW   
 Severity: Unknown
 Priority: Normal
 Component: Sys.Web
-AssignedTo: gonzalo at ximian.com                            
+AssignedTo: robertj at gmx.net                            
 ReportedBy: robertj at gmx.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 Summary: [PATCH] SetCacheability(HttpCacheability.Server) generates "Expires" header
@@ -66,6 +66,31 @@
 3. ServerAndPrivate emits "Vary: *"
 I'm not sure if I should deal with them. The first might
 break some existing mono ASP.NET apps which were never tested
 under Windows. The 2nd is something for ancient HTTP 1.0 proxies.
+------- Additional Comments From gonzalo at ximian.com  2006-03-21 12:50 -------
+Just for the record:
+* A Expect header equals to the Date header means that the data sent
+in the response is expired (RFC 2616, 14.21), so that shouldn't be an
+* A Expect header that has an invalid date format is treated as if the
+data was expired (RFC 2616, 14.21), so sending a -1 is not harmful.
+* Cache-Control "no-cache" without parameters and "private" are
+equivalent (RFC2616, 14.9.1).
+* Pragma "no-cache" is used for backwards compatibility with HTTP/1.0
+So we're not doing that bad before the patch, apart from those
+"serverand*" :-)
+Anyway, the patch looks good (apart from that leftover form the
+validation callback patch). Can you commit to HEAD and 1-1-13?
+Thanks a lot.

More information about the mono-bugs mailing list