Home Dashboard Directory Help
Search

Tweaks to System.Web.HttpCachePolicy (ASP 2.0) by Laurence Hygate


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Suggestion
ID: 212646
Opened: 9/26/2006 8:21:37 AM
Access Restriction: Public
1
Workaround(s)
view

Description

SetLastModified assumes that the web server's clock is authoratitive with its check for future times.
SetEtag doesn't work if cacheability is set to private.
Details
Sign in to post a comment.
Posted by Microsoft on 2/1/2007 at 12:49 PM
Thanks for your feedback on the .NET Framework! S. Somasegar, the Developer Division VP recently

wrote in his blog (http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx) on how the next

release of the .NET Framework (codename “Orcas”) requires a high degree of backward compatibility

and therefore, how we are being very strict about the number and scope of bugs that are fixed and

features that are added in the “Red Bits” during Orcas. Unfortunately, this bug falls into the red

bits category, and so we are not able to address it in Orcas due to the potential for it to

introduce compatibility issues.

We recognize you submitted this bug because of a specific problem you are experiencing with the

product. If you submitted this bug because of a blocking problem you’re experiencing and continue

to experience, you may want to contact Microsoft Professional Services

http://support.microsoft.com. Alternatively you may find additional information by searching or

posting to the ASP.NET forums (http://forums.asp.net). Finally, if you submitted this bug

because of a blocking problem you’re experiencing and continue to experience, you may want to also

open a support call with Microsoft Professional Services

(http://support.microsoft.com/?LN=en-us&scid=gp%3Ben-us%3Bofferprophone&x=8&y=14), which is a

better support option when you’re experiencing business impact for your problem and are unable to

resolve it in a timely manner on forums or other support channels.

Before starting work on the next full release of the .NET Framework, we will review the Connect

data to help us identify and address the top customer reported issues. We’ll broadly review all

bugs submitted to date at that time.

The .NET UI Frameworks Team
Sign in to post a workaround.
Posted by Laurence Hygate on 9/26/2006 at 8:26 AM
I subtract 5 minutes of the database stored time and use that as the Last-Modified header. I use NTP to make sure that the clocks don't drift too far apart.

No workaround yet for the Etag issue