RE: Cache-control and Expires headers

[WALDO]

I am having the exact same problem. I am using VS2008 (.Net 3.5) and I
can't set the Expires date out any further than one day.

Doing a little reflection, I see that in the HttpCachePolicy class,
SetExpires() method, if the expires is already set, it will only change
if the new expiration date is less than the existing one.

I have removed all of my custom HttpModules and discovered that none of
mine are setting the expiration.

Somwhere in the pipeline, something built in is pre-setting the
expiration date to one day forward from the request.

I experience the same effect whether I use Response.Cache.SetExpires(),
Response.Expires, or Response.ExpiresAbsolute.
Sometimes the greatest solutions come from the simplest logic.
Being told "No" is merely the incentive to do it anyway.

*** Sent via Developersdex http://www.developersdex.com ***

[Steven Cheng [MSFT]]

Thanks for your inputs.

I've also forwarded this question to some other ASPNET dev engineers. I'll
post here is if there is any further information about this issue.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>Subject: RE: Cache-control and Expires headers

>Newsgroups: microsoft.public.dotnet.framework.aspnet
Date: Wed, 07 May 2008 07:08:20 -0700

>I am having the exact same problem. I am using VS2008 (.Net 3.5) and I
can't set the Expires date out any further than one day.

Doing a little reflection, I see that in the HttpCachePolicy class,
SetExpires() method, if the expires is already set, it will only change
if the new expiration date is less than the existing one.

I have removed all of my custom HttpModules and discovered that none of
mine are setting the expiration.

Somwhere in the pipeline, something built in is pre-setting the
expiration date to one day forward from the request.

I experience the same effect whether I use Response.Cache.SetExpires(),
Response.Expires, or Response.ExpiresAbsolute.
Sometimes the greatest solutions come from the simplest logic.
Being told "No" is merely the incentive to do it anyway.

*** Sent via Developersdex http://www.developersdex.com ***

[Steven Cheng [MSFT]]

Hi Mike & WALDO,

After some further discussion with some other engineers, they said that the
one 1 day fixed expire value is not the exact behavior and the actual code
logic is a bit different from that. For the problem you encounter, it might
be a specific issue. Due to the support limitation in newsgroup, it is a
bit hard for me to further involve them. If this is an important issue, I
would suggest you consider contacting CSS for further troubleshooting:

Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

>From: st*****@online.microsoft.com (Steven Cheng [MSFT])
Organization: Microsoft
Date: Fri, 09 May 2008 06:16:47 GMT
Subject: RE: Cache-control and Expires headers

>
Thanks for your inputs.

I've also forwarded this question to some other ASPNET dev engineers. I'll
post here is if there is any further information about this issue.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

================================================= =
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ault.aspx#noti

f

>ications.

================================================= =
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>>Subject: RE: Cache-control and Expires headers

>>Newsgroups: microsoft.public.dotnet.framework.aspnet
Date: Wed, 07 May 2008 07:08:20 -0700

>>I am having the exact same problem. I am using VS2008 (.Net 3.5) and I
can't set the Expires date out any further than one day.

Doing a little reflection, I see that in the HttpCachePolicy class,
SetExpires() method, if the expires is already set, it will only change
if the new expiration date is less than the existing one.

I have removed all of my custom HttpModules and discovered that none of
mine are setting the expiration.

Somwhere in the pipeline, something built in is pre-setting the
expiration date to one day forward from the request.

I experience the same effect whether I use Response.Cache.SetExpires(),
Response.Expires, or Response.ExpiresAbsolute.
Sometimes the greatest solutions come from the simplest logic.
Being told "No" is merely the incentive to do it anyway.

*** Sent via Developersdex http://www.developersdex.com ***