MEGA Search
20.3 Million


Sign Up
From: Steff  
Subject: How: force idHTTP with proxy to "no-cache"?
NewsGroup: borland.public.delphi.internet.winsock
Date Posted: 24-Feb-2003 at 0:0:8 PST
Hi!

How to force TidHTTP to read the current values of a
webserver instead of using the "old" cached on in the
proxy-server?

It's a XML-File, which should be retrieved directly 
by a Get-Command.

I allready tried
      Http.Request.Pragma := 'no-cache';
      Http.Request.CacheControl := 'no-cache';
but this doesn't work very fine :(

Any other idea? I don't know, which kind of proxy 
my customers will work with, so the solution has to
work with (as far as possible) any kind of proxy and
any kind of HTTP-Version.

Any idea?!

  Steff

From: Stephane Grobety  
Subject: Re: How: force idHTTP with proxy to "no-cache"?
NewsGroup: borland.public.delphi.internet.winsock
Date Posted: 24-Feb-2003 at 1:19:36 PST
> How to force TidHTTP to read the current values of a
> webserver instead of using the "old" cached on in the
> proxy-server?

Well: you can't... If the proxy server doesn't honor the no-cache
request, then the only way is to query the web site directly (that is,
remove the proxy).

Good luck,
Stephane

From: Grahame Grieve  
Subject: Re: How: force idHTTP with proxy to "no-cache"?
NewsGroup: borland.public.delphi.internet.winsock
Date Posted: 24-Feb-2003 at 19:31:2 PST
Steff wrote:
> Hi!
> 
> How to force TidHTTP to read the current values of a
> webserver instead of using the "old" cached on in the
> proxy-server?
> 
> It's a XML-File, which should be retrieved directly 
> by a Get-Command.
> 
> I allready tried
>       Http.Request.Pragma := 'no-cache';
>       Http.Request.CacheControl := 'no-cache';
> but this doesn't work very fine :(
> 
> Any other idea? I don't know, which kind of proxy 
> my customers will work with, so the solution has to
> work with (as far as possible) any kind of proxy and
> any kind of HTTP-Version.
> 

good luck. proxies are notorious for ignoring
the rules. some are sticklers and some aren't.

if you control the back end, you can throw a
random number into the url. This not only meets
your goals, it also fills up the cache with crap ;-)

another alternative is to post instead of get.
post responses aren't supposed to be cached either.

Grahame