I can only presume you are requesting a different caching strategy then surge currently gives you however I'd like to talk you off this ledge. As it stands surge provides a caching algorithm that ensures the same file is never distributed to the same client more than once per year as well as never displays a stale file, EVER.
If you are looking for a more aggressive caching strategy we strongly suggest using an approach that does not have a dependency on a persistent network connection. This can be done with either a service worker or in some (but more limited) circumstances app cache manifest could work for you.
You can read more about the app cache circumstances @sintaxi mentioned in this article I wrote for David Walsh: Don’t Wait for ServiceWorker: Adding Offline Support with One-Line (Surge builds your appcache file automatically as a fallback, which hopefully buys you more time to focus on ServiceWorker instead!)
I can only presume you are requesting a different caching strategy then surge currently gives you however I'd like to talk you off this ledge. As it stands surge provides a caching algorithm that ensures the same file is never distributed to the same client more than once per year as well as never displays a stale file, EVER.
If you are looking for a more aggressive caching strategy we strongly suggest using an approach that does not have a dependency on a persistent network connection. This can be done with either a service worker or in some (but more limited) circumstances app cache manifest could work for you.