Question How to stop Safari caching data, or, alternatively, disable Safari's "Back" button ?

[jasonlutes2001]

Hello,

I am running a 9th generation iPad with Safari Safari version 15.5. I am setting it up to run in kiosk/guided access mode to run a webform that will be used by multiple people. In doing so, I need to either stop the browser from caching any information at all, or disable the back button. Guidance on both would be the most helpful. I am not proficient at all with JavaScript, but I do know how to set it up so the browser can use it. Any ideas?

Thanks,
Jason

 

[rgd1101]

do they login or not?
it this intranet site/pages that you create? there are html meta tag for no cache

 

[jasonlutes2001]

do they login or not?
it this intranet site/pages that you create? there are html meta tag for no cache

This is not an intranet page. It is an unlisted internet page extension from our main site. And no, they do not login to it. What is the html meta tag for no caching?

 

[hotaru.hino]

https://cristian.sulea.net/blog/disable-browser-caching-with-meta-html-tags/

There's also no practical way to disable the back button on the browser from the page. The only way to get around this is to create the page as a single page application run entirely with AJAX. But even then, pressing "back" means the user loses all progress of where they were.

 

[jasonlutes2001]

https://cristian.sulea.net/blog/disable-browser-caching-with-meta-html-tags/

There's also no practical way to disable the back button on the browser from the page. The only way to get around this is to create the page as a single page application run entirely with AJAX. But even then, pressing "back" means the user loses all progress of where they were.

That is exactly what I want. I want the user to not have access to any information that might temporarily be cached in if they hit back.

 

[hotaru.hino]

That is exactly what I want. I want the user to not have access to any information that might temporarily be cached in if they hit back.

This is a problem then, because as I said, it requires AJAX, which means Asynchronous JavaScript and XML (though the XML part is actually optional). You're going to have to learn JavaScript to create a single-page application. Worse still, you need a server that can handle AJAX style requests (though the server can be made with anything). So you can't have a basic web server that just throws out HTML/CSS.