nenbpjkdpicondajamolnlnpphkdjefi
The Local File Server extension enables web sites to link to local files via "http://localhost/" URLs. For security reasons, Chrome blocks "file://" URLs to local files in remote web pages. Some web services, like for instance Gmail, don't even render such URLs. Though, there are circumstances where links to local files are secure and desirable. For example, a local process, like a backup job, may want to send execution logs via email that contain links to local files. If the generated email includes "file://" URLs and the email is read in Gmail, the URLs won't even be rendered and even if they were rendered, Chrome (and most other browsers) would block them. Thanks to the Local File Server extension, the process can instead include "http://localhost/" URLs. These will be rendered in all email clients, they won't be blocked by any browser, and the extension will redirect them to the desired local file (provided the URLs are accessed from the machine where the files live). The syntax for local file URLs is http://localhost/file.html?path= where is the absolute path to the desired local file. No "file://" prefix is allowed in the path. Forward slashes (/) (not backslashes (\)) must be used as directory separators (even on Windows systems). All paths must start with a forward slash (/). Here are a few working examples for different systems: - Linux: http://localhost/file.html?path=/home/ links to the /home/ directory. - macOS: http://localhost/file.html?path=/System/ links to the /System/ directory. - Windows: http://localhost/file.html?path=/C:/Windows/ links to the C:\Windows\ directory. Malicious third parties could abuse http://localhost/ URLs to access your local files. For that reason, when a http://localhost/file.html?path= URL is clicked, the Local File Server extension doesn't directly open the desired file. Instead, it renders a page that displays a link with a "file://" URL and a warning to only click on it if one was brought there via a trusted party. If one clicks on the link, the file designated by is opened (provided the link is accessed from the machine where the file lives). The extension allows the creation of direct local file URLs that avoid the need to click twice and immediately open the designated file. Their syntax is http://localhost/file.html?path=&access-key= where is the access key stored in the Local File Server extension. When the extension is installed, a cryptographically secure access key is generated. It can be viewed and changed on the extension's options page. The key must be kept secret to prevent malicious third parties from being able to craft valid direct local file URLs. The key should only be shared with trusted parties that need to create direct local file URLs. If the access key is ever leaked, set a new one in the extension (via it's option page). Old direct URLs will still work but instead of directly opening the linked files, they will render the same page as URLs with no access key and thus require a second click to actually open the designated file. For any questions, comments or bug reports, please contact me via the developer email listed below or use the tools available in the Support section below.
HTTP Nowhere
This extension upgrades non-secure connections (HTTP) to secure (HTTPS). If the web site does not correctly support HTTPS, Chrome will refuse to connect (with the usual interstitial warning page). Thus, this extension will make it hard to view some web sites. For maximum safety, you should also turn on Chrome’s Secure DNS (DNS over HTTPS) feature. There is no way (yet?) for an extension to turn this on for you, so you have to do it manually. To do so, go to the dots menu → Settings → Security, and then scroll down to Use Secure DNS. Select a provider or fill in your own. (You can also get to this setting by navigating to the URL chrome://settings/security?search=dns.) HTTP Nowhere is designed to be as simple as possible, and has no functionality other than upgrading connections. This is easy to see in the very short and simple implementation. It needs no special permissions or access to the web pages you view. There is nothing to configure; HTTP Nowhere is either on or off.
Convert to localhost
Convert your current URL to localhost This extension can be used to convert the URL in your current tab to use http://localhost:$port instead of the current domain. Port is configurable in the options of the extension.
Live Server Web Extension
Makes your existing server live. This is a browser extension that helps you to live reload feature for dynamic pages Live Server - Makes your existing server live - this is a Web Extension that helps you to live reload feature for dynamic content (PHP, Node.js, ASPNET -- Whatever, it doesn't matter). This extension is for Live Server (VSCode Extension - required v3.0.0+). You have to install Live Server extension for vscode in order to use this Add On. Follow this link to setup : https://github.com/ritwickdey/live-server-web-extension#setup Note: This is an open source project and it doesn't collect *any* data. Demo : https://raw.githubusercontent.com/ritwickdey/live-server-web-extension/master/img/screenshots/live-server-web-extension.gif
Local Host Hot Swap
Swap the root domain for localhost on your active tab. Swap your current url to => localhost or localhost with a port number. The extension will remember your last entered port number.