Localhost HTTPS -> HTTP

HTTPS Everywhere

Navigate the web with confidence! HTTPS Everywhere is a Chrome extension designed to enhance your internet security with a simple yet powerful action: it automatically redirects you to the HTTPS version of websites whenever possible. - Automatic HTTPS Redirect: Seamlessly switches your connection from HTTP to HTTPS, ensuring that your browsing is encrypted and more resistant to eavesdropping. - Improved Privacy: Protect your sensitive information from prying eyes, especially on public Wi-Fi networks. - User Notifications: If you land on a webpage that doesn't support HTTPS, the extension will alert you, keeping you informed about your security status. - Simple & Lightweight: Runs quietly in the background without slowing down your browsing experience. - Regular Updates: The extension is maintained with regular updates to ensure compatibility with the latest websites and security standards.

HTTP to HTTPS Redirector

Redirects HTTP to HTTPS with enable/disable functionality. HTTP to HTTPS Redirector 🌐🔒 Enhance your web security effortlessly with the HTTP to HTTPS Redirector Chrome extension. Automatically upgrade your HTTP connections to secure HTTPS and enjoy: ✨ Automatic HTTPS Upgrades: Secure all your web traffic seamlessly. 🔄 Enable/Disable Toggle: Easily turn the redirection on or off. 🌍 Localhost Bypass: Skip HTTPS for localhost during development. 📈 Redirect Analytics: Track the number of redirects performed. 🚫 Manage Exclusions: Exclude specific domains from redirection. 🔔 Real-time Notifications: Get alerts for each redirect. Protect your online privacy and browse with confidence!

Localhost Cookie Sync

Sync cookies from a domain to your localhost Keep certain cookies synced from a domain to your localhost. This can be a good tool to use by keeping things like authentication tokens from a domain synced to your local dev environment.

Local File Server

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.