so stunnel doesnt rewrite the headers besides the encryption? does that mean only stunnel can receive traffic forwarded by itself, and can only work if both ends of the tunnel are defined and connected?
On 12/18/18, Ludolf Holzheid lholzheid@bihl-wiedemann.de wrote:
On Tue, 2018-12-18 17:49:16 +0100, kovacs janos wrote:
[..]
does this mean stunnel encrypts requests differently than browsers? or the connection between browser and proxy is different than stunnel and proxy?
Janos,
Making HTTPS from HTTP is a bit more than just encrypting/decrypting. To make this work, you have to re-write HTTP headers and links in the HTTP body before encrypting and after decrypting. As these are part of the TCP payload, you have to follow, parse and modify the data streams exchanged between client and server, in addition to encryption.
HTH,
Ludolf
--
Ludolf Holzheid
Bihl+Wiedemann GmbH Floßwörthstraße 41 68199 Mannheim, Germany
Tel: +49 621 33996-0 Fax: +49 621 3392239
mailto:lholzheid@bihl-wiedemann.de http://www.bihl-wiedemann.de
Sitz der Gesellschaft: Mannheim Geschäftsführer: Jochen Bihl, Bernhard Wiedemann Amtsgericht Mannheim, HRB 5796 _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users