Hi there,
Is it possible JWT ignores meta headers ? We're trying to set headers to
make sure IE does no caching at all. A classic I presume. :-)
*WApplication.addMetaHeader("cache-control", "max-age=0");*
*WApplication.addMetaHeader("cache-control", "no-cache");*
*WApplication.addMetaHeader("expires", "0");*
*WApplication.addMetaHeader("expires", "Tue, 01 Jan 1980 1:00:00 GMT");*
*WApplication.addMetaHeader("pragma", "no-cache");*
The aforementioned code has no effect on the generated html page.
The mystery is elucidated when looking to the source code. It maintains a
list of meta headers, but nowhere is this list used to build pages.
Moreover it is assumed the meta header names are unique for each page.
However, in order to cope with different browsers, the same meta header
must be repeated. Each header targets a different browser.
Is this on the roadmap of JWT ?
Regards,
Jan
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
