04-12-2018, 08:20 PM
By default forms are not cached anyway. The only content that normally is cached are resources you might reference in a form such as static images etc.
If you are serving content via content handler that can and often is cached. Those items you listed in the case of content handlers can tell the browser not to cache them.
In the end though, browser can and will cache things in the short term as its just how they work. However once a page is gone and the resources to it are no longer needed, then if you have specified no cache it should dispose of them.
You can use the browser debuggers to look at resources and the headers sent down the pipe for each.
In Chrome you can observe the cache with:
chrome://cache/
or a plugin (not tested, just found it in Google) like this:
https://chrome.google.com/webstore/detai...cpbd?hl=en
If you are not using SSL, that can help as well with security and caching in some cases.
In short, disable caching as per above and then observe and report using manual inspection.
If you are serving content via content handler that can and often is cached. Those items you listed in the case of content handlers can tell the browser not to cache them.
In the end though, browser can and will cache things in the short term as its just how they work. However once a page is gone and the resources to it are no longer needed, then if you have specified no cache it should dispose of them.
You can use the browser debuggers to look at resources and the headers sent down the pipe for each.
In Chrome you can observe the cache with:
chrome://cache/
or a plugin (not tested, just found it in Google) like this:
https://chrome.google.com/webstore/detai...cpbd?hl=en
If you are not using SSL, that can help as well with security and caching in some cases.
In short, disable caching as per above and then observe and report using manual inspection.