Client caching

  • Thread starter Thread starter Hector Correa
  • Start date Start date
H

Hector Correa

I really don't know why your having that problem. What I
do know is that .NET automatically treats URLs with a dot
in them (like http://172.16.1.206/) different from URLs
without the dot (like http://machinename/)

..NET considers a URL with a dot as an "internet" URL and
applies certain (security) policies. A URL without the
dot is (by default) considered as an "intranet" URL.

With this in mind, it seems that .NET is using different
caching policies for internet addresses from intranet
addresses.

To verify this, try adding http://172.16.1.206 as a
trusted URL in IE Local Intranet Zone. I realize you
don't want to mess with IE, but this at least will let
you know if what I am saying is true.

If the caching problem is fixed after this, then you
should probably look at the .NET Configuration Tool to
configure your site in such a way that the caching work
as you expect. If all I've said does not work, then,
well, it was a shot :)
 
Thanks Hector. I solved the caching problem by enabling
content expiration of HTTP headers at IIS. I have set that
to Expire immediately.
 
Back
Top