Make stored persistent data location configurable

Looking through the code implementation for the cached path, the persistent data path is initialized using a MD5 hash of the url of the page, where the search query part (?foo) of the URL is removed.
The url field comes from initialization code at

Code (CSharp):

1.     core::string url = GetStringFromJS(JS_SystemInfo_GetDocumentURL);
2.     InitializeWebGLPersistentDataPath(url);
3.  

which is from JavaScript side in SystemInfo.js:

Code (JavaScript):

1.     JS_SystemInfo_GetDocumentURL: function(buffer, bufferSize)
2.     {
3.         if (buffer)
4.             stringToUTF8(document.URL, buffer, bufferSize);
5.         return lengthBytesUTF8(document.URL);
6.     },

So according to this, the IDBFS persistent data path is "/idbfs/<md5hash(document.URL)>", and hence should stay the same on each rebuild. (looking at Unity 2020.2 code)
I wonder if I missed something here. Do you use the same online URL for the game when you upload a new version, or does that change?
If you are changing the location, then what you can try to locally work around is to create a file named "DocumentUrl.jslib" in the Assets/ directory of the project, with the contents

Code (JavaScript):

1. mergeInto(LibraryManager.library, {
2.     JS_SystemInfo_GetDocumentURL: function(buffer, bufferSize) {
3.         var myDocumentUrl = 'https://crazygames.com/mygame';
4.         if (buffer)
5.             stringToUTF8(myDocumentUrl, buffer, bufferSize);
6.         return lengthBytesUTF8(myDocumentUrl);
7.     }
8. });
9.  

and do a rebuild of the project. Then verify in a Development build that this function can be found in the generated .framework.js file. After that the hash name of the IndexedDB repository should stay the same.

 

Oh, this is a gaming portal type of scenario. Gotcha.

Does every game reside on their own (sub)domain so that they don't stomp on each other's data? If rebuilding in the game is not feasible, how do would such a configuration then be deployed? We could entertain the option of adding a build setting or a field in the .html template, but in any case, the project will need to be modified somehow?

 

That sounds like a separate problem from @CrazyGamesCom above. He is asking to be able to share the persistent data when launching from different URLs, you are asking to not share the persistent data when launching from the same URL?

 

My understanding is that he is using different folders for each game upload to avoid having to configure man-in-the-middle CDNs to flush their HTTP caches (and other HTTP caching problems)?