Some poor Webpages out of our client's control do not set the right HTTP headers, leading to possibility of sensitive form data to be exposed in a kiosk setting.
RE
https://groups.google.com/forum/#!msg/webc-users/TxsyvRqqJpY/iESEqvOzHAAJ
We need to explore overriding a bad page by manipulating HTTP headers by adding:
- no-cache
- no-store
- must-revalidate
I saw explore, because this blanket feature enabled on Website might cause havoc.
Some poor Webpages out of our client's control do not set the right HTTP headers, leading to possibility of sensitive form data to be exposed in a kiosk setting.
RE
https://groups.google.com/forum/#!msg/webc-users/TxsyvRqqJpY/iESEqvOzHAAJ
We need to explore overriding a bad page by manipulating HTTP headers by adding:
I saw explore, because this blanket feature enabled on Website might cause havoc.