Wrong absolute expiration is used about referencesource HOT 5 CLOSED

This is not the right repository to file issues about the bug, the referencesource repo is read-only.

@terrajobst can you please advise about where such issues should be filed? I think we should also add issue and pull request templates here which explain the distinction. LOL, seems this is already there now :)

from referencesource.

I can confirm this is happening to me on two of my three developer machines using this Cache.Insert signature taking these four parameters (System.Web.Caching.Cache).

What framework update did this go out with? The code in question hasn't been touched in years and in passing in DateTime.Now + two hours. We change it the DateTime.UtcNow and it works again OR if we manually add 9 hours to our DateTime.Now calc (7 for UTC)....

On several other developer machines this hasn't happened yet and on zero servers.... Figure it's an update to the framework via Visual studio update perhaps?

from referencesource.

https://github.com/Microsoft/referencesource/blob/455f59f089ff2e96375e800c9b7866446f16cb30/System.Web/Cache/cache.cs#L425

from referencesource.

This appears to have been in the framework for a long time as is..... Not sure why it's now manifesting on some machines here and not others with the code we wrote for cache.insert not being changed itself since 2015..... Must be something interrelated with a machine change....

from referencesource.

@swcarter007

I suggest you file the issue in aspnet/home repository. We only track reference source infrastructure issues here.

from referencesource.