Re: Fernando Caba's question

Dear Anthony/Fernando,

> Fernando Caba <fcaba@criba.edu.ar> writes:
> > The first problem is when any user in Netscape press the
> > reload button, the first proxy (proxy-http) request the page to the
> > second proxy, and this request to the provider too. Why don't any of the
> > two proxies cached the pages????!!!!!
>
> When you hit reload, Netscape adds a "no-cache" tag to the request, saying
> it wants the original page, not the version cached on any intermediate
> proxy. It's the user's way of saying "I think this page has been modified
> since I first loaded it". This can be very useful when you have a telnet
> window open to edit HTML source and you want to see what you've accomplished
> so far.
>
Not entirely true... Only when you do a Forced Reload (pressing SHIFT while
clicking Reload in netscape) it will add a Pragma: no-cache. If you press
just "Reload", the caching server will get it with a "If-Modified-Since Get"
(result-code 304)

Cheers, Henny

-- 
-----------------------------------------------------------------------------
E-Mail: Henny.Bekker@cc.ruu.nl    ! Disclaimer: The main obstacle to progress
http    http://www.ruu.nl/~henny  !             progress is not ignorance,but
PTT:    Voice: +31 30 2536971 Fax: +31 30 2531633 ! the illusion of knowledge
X400:   /G=Henny/S=Bekker/OU=cc/O=ruu/PRMD=surf/ADMD=400net/C=nl         o
Paper:  H.J.Bekker, Utrecht University, Computer Centre              _  /- _
        Po Box 80011, 3508 TA  Utrecht  Nederland                   (_) > (_)
-----------------------------------------------------------------------------