Re: IIS6 caching

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Egbert Nierop \(MVP for IIS\) (egbert_nierop_at_nospam.invalid)
Date: 10/10/04 

Date: Sun, 10 Oct 2004 10:56:08 +0200

"M. M. Rafferty" <mmr@vistagrande.com> wrote in message
news:O90mZXkrEHA.2000@tk2msftngp13.phx.gbl...
> We've run into a situation with Windows 2003 Web server edition where IIS
> 6
> caching and continuing to server old content after the source files has
> been
> edited.
>
> Initially the hosting client contacted us and it appeared to be a caching
> issue on there end. There was no indication in the webserver log that
> there
> had been a recent request from their IP for the involved pages. I was
> able
> to bring up the pages and see the changed content. We decided it was
> simply
> a client site or proxy caching issue.
>
> Today, we received a second frantic call. They were still having problems
> with the caching and needed to have certain changes completed (legal
> requirements.) No matter what they did, they were not seeing the
> revisions
> which had been uploaded with the built-in IIS 6 FTP service. They had a
> couple additional one line changes that needed to be made, and I used
> notepad to edit their HTM file on the server. I had no trouble initially
> seeing the change. But it wasn't quite right and when I went back to
> change
> the file a second time, the changes just would not appear. I went through
> the drill of clearing the browser cache. No change. I tried a different
> browser and still no change. Tried from the web server itself and it was
> also showing the old version. And in these cases, the web server logs
> were
> showing the hits. I finally gave up and recycled their application.

> Why is IIS not getting the message that the pages have changed? There is
> no
> third party application to blame. Just NotePad and IIS/FTP being used.
> It
> is not acceptable to have require the administrator to recycle the
> application in order to get the latest changes by one of the hosting
> clients' web developers to be served.
>
> Is this a known issue with IIS 6? If so, is there a patch to correct it?

What do they upload? Static HTML or aspx pages? In the last case, ALSO the
bin directory needs to be uploaded with a new assembly.
In addition, your client is using IE to test it? Because depending on the
client type it might ask IIS to send an creation timestamp where the next
time, IIS might indicate that the content has not changed. If that is the
case, you should modify code to include a timestamp based on the assembly
Response.Cache... start here...

>
> Thanks,
> Mary Rafferty.
>
>

Relevant Pages

  • Re: IIS6 caching
    ... The caching was not in the browser. ... IIS 6 was serving stale content. ... >>> a client site or proxy caching issue. ... Tried from the web server itself and it ...
    (microsoft.public.inetserver.iis)
  • RE: Autodeployed Win App - Vista IIS 7.0
    ... Here are the configurations for the Web Server and the Client. ... Client: ... Vista, IIS 7, IE 7 ... RE "exe.config file on the web server is set to use a local path" on IIS 5 ...
    (microsoft.public.dotnet.general)
  • Re: IIS6 caching
    ... The caching was not in the browser. ... There was no proxy server ... IIS 6 was serving stale content. ... >> a client site or proxy caching issue. ...
    (microsoft.public.inetserver.iis)
  • Re: How does the connection work?
    ... It's hosted on the client machine like the IE a browser is hosted on the client machine. ... does it come back into IIS as a outside ... Session information is kept in a cookie on the client machine used by a browser or it's a cookieless session and session information is coming in the HTTP traffic between the client and the Web server. ...
    (microsoft.public.dotnet.languages.csharp)
  • IIS6 caching
    ... We've run into a situation with Windows 2003 Web server edition where IIS 6 ... Initially the hosting client contacted us and it appeared to be a caching ...
    (microsoft.public.inetserver.iis)