How to build WebPages?

[Bruno Alexandre]

Hi Guys,

I have several problems on the company website...

the major one is that the IE saves the pages and (even if you log out
and log in again) it shows THAT pages instead a refresh version of the page.

how can I prevent that?


probably using session identifier, to show something like

http://www.filtrarte.com/Xa129ce9c98ce9f9f999e6bd4c050/portal/default.asp

instead
http://www.filtrarte.com/portal/default.asp

but I don't know how.

is there anyone who could help me on this?

I know this is a ASP.NET Forum and I use only ASP but I can't find any asp
newsgroups and I thought that ASP.NET and ASP are similar regarding
sessions, so I give it a shot.

--


Bruno Miguel Alexandre
Dep Informática do Grupo Filtrarte

Av General Humberto Delgado, 91
Vila Verde
2705-887 Terrugem SNT
Portugal

T. +351 219 608 130
F. +351 219 615 369
w. www.filtrarte.com
@. (e-mail address removed)

 

[Mark Fitzpatrick]

Check out http://www.htmlgoodies.com/beyond/nocache.html for info on adding
no-cache meta tags. Basically though, trying to make things like cookieless
session identifiers causes more work for you then it should. Check your own
IE settings and make sure they are set to load the page automatically or
every time you hit the page. Usually it's set to automatically by default.
This will often mean that it will check for a new page the first time, but
when you re-visit the page unless you hit F5 to refresh the page, which
should then force it to check for a newer page. If you still don't get it to
refresh then it could be a problem you won't be able to handle, ISP caching.
Some ISPs cache pages to decrease demands on their network. AOL used to be
very bad at this, especially when they were first getting really connected
into the internet as they only had a certain amount of pipeline to go
through. If an ISP caches a page there won't be much at all that can be done
to over-ride it. Their caching algorithms may even ignore cookieless session
ids in the URL as well. Basically though, your best bet is to stick with the
simplest and use the meta pragma tags for controlling caching, and add code
in your ASP pages that will force them to expire after something like 20
minutes or so.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage