Found this on http://www.i18nguy.com/markup/metatags.html

The directive CACHE-CONTROL:NO-CACHE indicates cached information should not 
be used and instead requests should be forwarded to the origin server. This 
directive has the same semantics as the PRAGMA:NO-CACHE.
Clients SHOULD include both PRAGMA:NO-CACHE and CACHE-CONTROL:NO-CACHE when 
a no-cache request is sent to a server not known to be HTTP/1.1 compliant.
Also see EXPIRES.
Note: It may be better to specify cache commands in HTTP than in META 
statements, where they can influence more than the browser, but proxies and 
other intermediaries that may cache information


Appearently, the directive 'PRAGMA:NO_CACHE' is not enough in the header.

I think, to be sure, I should add a dummy-ID at the end of the URL with an 
integer value incremented on each request.
This way, the proxy will allway see a new URL.


Paul


----- Original Message ----- 
From: "Paul" <[EMAIL PROTECTED]>
To: <twsocket@elists.org>
Sent: Wednesday, April 26, 2006 5:12 PM
Subject: [twsocket] HttpCli.NoCache


> Hi,
>
> I get reports from some users that my application doesn't work behind a
> proxy.
> Each time the program connect to a server, it should receive a different
> string.
> Remote testing showed that the second time a request to the server is 
> made,
> it is answerred immediately by their local proxy.
> The HttpCli.NoCache is set to 'true' or is this a bug in HttpCli ?
> Is there anything else I should do to force their proxy to forward each
> request to our server ?
>
>
> Thanks
>
> Paul
>
>
> -- 
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
> 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to