469,271 Members | 1,009 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,271 developers. It's quick & easy.

Changes to .asp file not updated to web

If the developers make changes to .htm files the saved
changes are updated to the web instantly, but if they
change a .asp file the change does not show on the site,
why is this?

please help

thank you

Jul 19 '05 #1
5 1676
That is not what is really happening. Computers do what they are told to
do, so I'd say that the user is not telling a computer the right thing,
whether it's the computer that's supposed to save the file, upload it, load
the page (not from cache), etc.

Ray at work

"kyle" <an*******@discussions.microsoft.com> wrote in message
news:03****************************@phx.gbl...
If the developers make changes to .htm files the saved
changes are updated to the web instantly, but if they
change a .asp file the change does not show on the site,
why is this?

please help

thank you

Jul 19 '05 #2
let me start this over

I can watch one of the developers open a .asp file in
FrontPage, make a change, save it back to the location it
was opened from x:\IntPub\<pagename>.com\www\<filename>.asp
But when I go to the webserver and open the IIS mmc, and
look at the <filename>.asp file uner <pagename>.com it is
not updated, and if browsed from the internet the site
still shows the old content on that page

But if on the webserver I go to
x:\IntPub\<pagename>.com\www using windows explorer I see
that the file is stamped with a date and time that match
the change, I can open the file from this location in IE
and see the change, and open the file in a text editor and
see the change made in the code

This is not the case with .htm files in the same
x:\IntPub\<pagename>.com\www any changes made to these
files post to the internet

-----Original Message-----
That is not what is really happening. Computers do what they are told todo, so I'd say that the user is not telling a computer the right thing,whether it's the computer that's supposed to save the file, upload it, loadthe page (not from cache), etc.

Ray at work

"kyle" <an*******@discussions.microsoft.com> wrote in messagenews:03****************************@phx.gbl...
If the developers make changes to .htm files the saved
changes are updated to the web instantly, but if they
change a .asp file the change does not show on the site,
why is this?

please help

thank you

.

Jul 19 '05 #3
"kyle" <an*******@discussions.microsoft.com> wrote in message
news:04****************************@phx.gbl...
let me start this over

I can watch one of the developers open a .asp file in
FrontPage, make a change, save it back to the location it
was opened from x:\IntPub\<pagename>.com\www\<filename>.asp
But when I go to the webserver and open the IIS mmc, and
look at the <filename>.asp file uner <pagename>.com it is
not updated, and if browsed from the internet the site
still shows the old content on that page

But if on the webserver I go to
x:\IntPub\<pagename>.com\www using windows explorer I see
that the file is stamped with a date and time that match
the change, I can open the file from this location in IE
and see the change, and open the file in a text editor and
see the change made in the code

This is not the case with .htm files in the same
x:\IntPub\<pagename>.com\www any changes made to these
files post to the internet


It could be a caching issue. I think that if you append some querystring
variables, you might be able to get around the caching. For example:
http://host/filename.asp?somefakevar=1

See if that does anything for you. If so, then it's probably just a matter
of the page being cached (in the browser or at some proxy between your
browser and the webserver). If not, then I'm not sure what to tell you...
it might still be a caching issue (I'm not sure if this method will actually
get around caching issues, but I thought I read once long ago that it
could).

Hope this helps.
Peter Foti
Jul 19 '05 #4
Kyle,
There are 2 places caching is occurring that can cause this problem:
First place is on the client's computer. To fix it go in IE to "Tools-->
Internet Options --> General Tab" and click the "Settings" button under the
"Temporary Internet Files" section. Under "Check for newer versions of
stored pages", select "Every visit to the page"

The second place is in IIS on the server. To fix this:
Open Administrative Tools --> IIS and navigate and select the web
application. --> Right-click --> properties. Click the "configuration"
button on the "Directory" tab. On the window that appears select the "Cache
Options" tab. Select the "do not cache ASP files" option.
Mike

"Peter Foti" <pe****@systolicnetworks.com> wrote in message
news:vq************@corp.supernews.com...
"kyle" <an*******@discussions.microsoft.com> wrote in message
news:04****************************@phx.gbl...
let me start this over

I can watch one of the developers open a .asp file in
FrontPage, make a change, save it back to the location it
was opened from x:\IntPub\<pagename>.com\www\<filename>.asp
But when I go to the webserver and open the IIS mmc, and
look at the <filename>.asp file uner <pagename>.com it is
not updated, and if browsed from the internet the site
still shows the old content on that page

But if on the webserver I go to
x:\IntPub\<pagename>.com\www using windows explorer I see
that the file is stamped with a date and time that match
the change, I can open the file from this location in IE
and see the change, and open the file in a text editor and
see the change made in the code

This is not the case with .htm files in the same
x:\IntPub\<pagename>.com\www any changes made to these
files post to the internet
It could be a caching issue. I think that if you append some querystring
variables, you might be able to get around the caching. For example:
http://host/filename.asp?somefakevar=1

See if that does anything for you. If so, then it's probably just a

matter of the page being cached (in the browser or at some proxy between your
browser and the webserver). If not, then I'm not sure what to tell you...
it might still be a caching issue (I'm not sure if this method will actually get around caching issues, but I thought I read once long ago that it
could).

Hope this helps.
Peter Foti

Jul 19 '05 #5
Will I have to re-start IIS if I make the change you
described in the second option?

thank you

-----Original Message-----
Kyle,
There are 2 places caching is occurring that can cause this problem:First place is on the client's computer. To fix it go in IE to "Tools-->Internet Options --> General Tab" and click the "Settings" button under the"Temporary Internet Files" section. Under "Check for newer versions ofstored pages", select "Every visit to the page"

The second place is in IIS on the server. To fix this:
Open Administrative Tools --> IIS and navigate and select the webapplication. --> Right-click --> properties. Click the "configuration"button on the "Directory" tab. On the window that appears select the "CacheOptions" tab. Select the "do not cache ASP files" option.
Mike

"Peter Foti" <pe****@systolicnetworks.com> wrote in messagenews:vq************@corp.supernews.com...
"kyle" <an*******@discussions.microsoft.com> wrote in message news:04****************************@phx.gbl...
> let me start this over
>
> I can watch one of the developers open a .asp file in
> FrontPage, make a change, save it back to the location it > was opened from x:\IntPub\<pagename>.com\www\<filename>.asp > But when I go to the webserver and open the IIS mmc, and > look at the <filename>.asp file uner <pagename>.com it is > not updated, and if browsed from the internet the site
> still shows the old content on that page
>
> But if on the webserver I go to
> x:\IntPub\<pagename>.com\www using windows explorer I see > that the file is stamped with a date and time that match > the change, I can open the file from this location in IE > and see the change, and open the file in a text editor and > see the change made in the code
>
> This is not the case with .htm files in the same
> x:\IntPub\<pagename>.com\www any changes made to these
> files post to the internet
It could be a caching issue. I think that if you append some querystring variables, you might be able to get around the caching. For example: http://host/filename.asp?somefakevar=1

See if that does anything for you. If so, then it's probably just amatter
of the page being cached (in the browser or at some
proxy between your browser and the webserver). If not, then I'm not sure what to tell you... it might still be a caching issue (I'm not sure if this method willactually
get around caching issues, but I thought I read once

long ago that it could).

Hope this helps.
Peter Foti

.

Jul 19 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by bobdirls | last post: by
4 posts views Thread by Glenn Owens | last post: by
3 posts views Thread by Waldy | last post: by
5 posts views Thread by keith.culpepper | last post: by
reply views Thread by Juan T. Llibre | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.