Is there some sort of cache built into the internal browser because when
I send a request to fetch my data from my web server I see the request
come in and the data go out the first time that the application is run.
Any further data requests appear to have a response, but nothing is
coming into or out of my extrnal data server (EWB appears to just reuse
the last lot of data that it got)

To fetch a fresh set of data I have to restart EWB.

--
Chris Holland
[Team Elevate]

Browsers always cache and it's desirable.

You need to ensure your web server  returns a "do not cache" header with your requests that should not be cached (not that you still likely want to cache images and other static parts).

Basically add header such as "Cache-Control: max-age=0" (or "Cache-Control: no-cache" should work also) to server response

Raul

<<
Chris Holland wrote:

Is there some sort of cache built into the internal browser because when
I send a request to fetch my data from my web server I see the request
come in and the data go out the first time that the application is run.
Any further data requests appear to have a response, but nothing is
coming into or out of my extrnal data server (EWB appears to just reuse
the last lot of data that it got)
>>

Hi,

This does not always prevent caching in my experience. I always add a param
to the url with a random number. This makes the call "unique".

"Raul" schreef in bericht
news:D32105BD-5F9E-4ACC-80FF-E5C7E8BA890B@news.elevatesoft.com...

Browsers always cache and it's desirable.

You need to ensure your web server  returns a "do not cache" header with
your requests that should not be cached (not that you still likely want to
cache images and other static parts).

Basically add header such as "Cache-Control: max-age=0" (or "Cache-Control:
no-cache" should work also) to server response

Raul

<<
Chris Holland wrote:

Is there some sort of cache built into the internal browser because when
I send a request to fetch my data from my web server I see the request
come in and the data go out the first time that the application is run.
Any further data requests appear to have a response, but nothing is
coming into or out of my extrnal data server (EWB appears to just reuse
the last lot of data that it got)
>>

Ronald,

<< This does not always prevent caching in my experience. I always add a
param to the url with a random number. This makes the call "unique". >>

If the resource has already been cached by the browser, then you need to
clear the browser's cache after making the cache-control changes on the
server side.  I've never seen any instance of cache-control not working
after that has been done.

Tim Young
Elevate Software
www.elevatesoft.com