WinInet Cache Location - certificate

Microsoft Windows ships with an API called WinInet, which is used, for example, for caching intermediate certificates fetched from AIA.
The microsoft documentation says:
If the retrieval URL is LDAP://, FTP://, or https://, then the
certificate (or CRLs) is also cached by WinInet in the local file
system. The actual location is the \Documents and
Settings\username\Local Settings\Temporary Internet Files folder.
However, this directory does not exist on current versions of Windows.
Where is this cache located on Windows 10/11?

Related

Where is JupyterLite notebook located locally on Windows?

I am using jupyterlite which is JupyterLab distribution that runs entirely in the browser.
However, after clearing the browser history, the files are no more visible.
Please let me know how can I retrieve the *ipynb files from my windows machine.
I have already checked %AppData% and I don't see any *ipynb files.
The files are stored in well... the browser. Specifically in the IndexDB or localStorage. This means that the physical location on the disk will depend entirely on the browser that you use, rather than on the operating system, and will likely be inaccessible (for an average user) without decoding binary blobs.
For example, in Chrome you can check the path to the application data using chrome://version/ (under Profile Path) and in that directory there should be IndexedDB folder. Then you need to find a sub-folder depending on the domain in which you accessed JupyterLite, for example https_jupyterlite.readthedocs.io_0.indexeddb.leveldb, and there you will find a LevelDB database file with .ldb extension and a MANIFEST file (with the pointer to the current version in the CURRENT file. The details of how to extract the blobs are outside of scope for this answer, but have a look at How to access Google Chrome's IndexedDB/LevelDB files?.
However, you can use files from your file system directly in JupyterLite without worrying about in-browser technologies with the jupyterlab-filesystem-access extension which uses File System Access API however this API is not available on Firefox yet.
As noted by #Wayne all of this is still quite experimental (both as in "using the newest browser APIs" and "the team of developers is still figuring way forward, please help by providing kind feedback and contributing").

How can I change VS Code Remote Server's default download folder?

I often download file from vscode remote server, but how could I change default download folder? It always opens a specific folder I don't want to download into.
I don't know about configuring the detault download directory, but there was an issue created and resolved to get VS Code to Remember target directory when downloading files #140358, which was implemented in commit ca936dc.
bpasero (one of the VS Code maintainers) commented to close that issue as resolved:
For the "Download" command we now remember the path where to download and restore that. This information is stored globally (i.e. applies to all windows) but will not roam via settings sync, because paths are typically machine local.
Previously we did a questionable computation of a default path that typically always ended up in the user home directory, which imho does not make a lot of sense for the download operation.
Verification:
connect desktop to any remote
right click from the explorer "Download"
pick a destination
repeat and verify the destination restores even across restarts

Collect resources (ie. properties files) for Install4J from remote machines

I need to collect a property file from a remote machine for my software to be installed using Install4J. Does Install4J provide functionality to collect/transfer files from remote locations to the local environment to proceed through installation?
You can use a "Download file" action to download a file from a URL to
${installer:sys.resourceDir}/my.properties
which is the temporary directory of the installer. In further actions you can refer to the downloaded file with the above syntax.

How does vscode handle file path when executing a language server remotely

I'm running a remote language server on with vscode via an extension I'm developping. Both client and server have access to the code via a mounted shared folder. The issue is that this folder is located on different places on the client and on the server. (/home/username/myproject on the client, /mnt/shared_folder/myproject on the server)
My question is can I configure the vscode language client so that it translates the path from the local location to the remote location and vice-versa?
If I'm running the language client from a project with a workspace, can I configure it so that it send file URI relative to the workspace root rather than sending the absolute file path? Doing so I can simply reconstruct the file uri on the server side with the path of the shared folder mount point.
I heard of Middlewares or uriConverters but I'm not sure if this the purpose they are intended to be used for.
Thank you!
It's expected by the Language Server Protocol that the URIs to reference files are the same on both server and client side.
I think the best is to place on the server (which after all is the one that has the "clone" of the files and not the orginal ones) the logic to turn the client URIs "/home/username/myproject" into server URIs "/mnt/shared_folder/myproject" when trying to access the files. Accessing the file is part of your implementation, so it's not something that's part of the LSP API, and conversion should happen inside your implementation.

After deploying via ClickOnce, where are the dlls stored on the client machine?

I read somewhere that config data is stored under user account->Local Settings->Application data, but can't find where the dlls, exes and resource files are going.
I know ClickOnce uses an application store and a data directory to store its application data, but are these accessible to the client? Are they browseable?
The dlls exes etc are all stored in the same folder. On my machine the root for each app is:
C:\Users\Robin\AppData\Local\Apps...
You can of course browse these with explorer...
On XP it is
c:\Documents and Settings\UserName(Sometimes called "Owner")\Local Settings\Apps\2.0\