Summary: This method is not recommended.
The only way to achieve this involves configuring your proxy as an HTTPS terminator, intercepting client connections and creating new ones to the destination site. However, this process is messy, unreliable, and insecure. It requires modifying data before sending it to the client, which can lead to complications.
Unfortunately, without the correct certificate, browsers will terminate the connection or raise warnings about invalid certificates. This can result in significant errors for clients, causing frustration and distrust.
To avoid these issues, installing a self-signed root certificate on all client machines may be necessary. While this allows for modified site displays, it breaks the trust chain established by TLS.
By compromising security measures like TLS, you become solely responsible for ensuring safe communication between clients and destinations. This puts sensitive information at risk of interception and compromise, undermining the purpose of secure connections.
Advanced security techniques like HTTP Public Key Pinning are actively working against such practices. Implementing these methods is crucial to protect against potential threats posed by unauthorized proxies.
In conclusion, it is strongly advised to refrain from implementing this method due to its inherent risks and detrimental effects on security protocols. Proceed with caution and prioritize safety over convenience.