[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
Sat Mar 18 20:08:43 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 robertj at gmx.net.


--- shadow/77826	2006-03-18 19:48:52.000000000 -0500
+++ shadow/77826.tmp.5166	2006-03-18 20:08:43.000000000 -0500
@@ -11,13 +11,13 @@
 AssignedTo: gonzalo at ximian.com                            
 ReportedBy: robertj at gmx.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
-Summary: SetCacheability(HttpCacheability.Server) generates "Expires" header
+Summary: [PATCH] SetCacheability(HttpCacheability.Server) generates "Expires" header
 Setting Response.Cache.SetCacheability(HttpCacheability.Server)
 still outputs an Expires-header. It has to omit the header in
 this case.
 See the test case of bug #77825.
@@ -48,6 +48,24 @@
 ------- Additional Comments From robertj at gmx.net  2006-03-18 19:48 -------
 Created an attachment (id=16640)
+------- Additional Comments From robertj at gmx.net  2006-03-18 20:08 -------
+The patch fixes only the Server & ServerAndNoCache cases,
+which are bugs.
+There are still differences between MS.NET and Mono
+(see attachment cc.txt):
+1. the default cc is "Cache-control: private" on MS.NET
+2. MS.NET (or is it just IIS?) always emits "Pragma: no-cache"
+   together with "Expires: -1"
+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.

More information about the mono-bugs mailing list