[stunnel-users] Web browsing over stunnel
josealf at rocketmail.com
Tue Nov 7 10:41:48 CET 2017
Peter made a very clear explanation. Note that your connect statement should be something like:
And you should test using something like:
> On Nov 6, 2017, at 6:52 PM, Peter Pentchev <roam at ringlet.net> wrote:
> On Mon, Nov 06, 2017 at 09:57:16PM +0000, Osvald Brko wrote:
>>> From: Josealf.rm <josealf at rocketmail.com>
>>> Sent: Friday, November 3, 2017 1:21 PM
>>> To: Osvald Brko
>>> Cc: stunnel-users at stunnel.org
>>> Subject: Re: [stunnel-users] Web browsing over stunnel
>>> It’s because the web site GETs a request for http://127.0.0.1/ not for http://www.stunnel.org/
>>> Just as an academic exercise, you may want to add this line to your hosts file (usually in \windows\system32\drivers\etc\hosts):
>>> 127.0.0.1 www.stunnel.net
>>> Then change your connect line to the IP address of www.stunnel..net (now 188.8.131.52 or 184.108.40.206).
>>> And test again.
>>> Jose Alfredo Diaz
>> I am not sure if I understand you right. What this academic exercise should reveal?
>> It just try to connect to 127.0.0.1 ...?
> The point is to get your browser to ask the remote server "give me the
> main page of www.stunnel.org" and not "give me the main page of
> 127.0.0.1". The webserver may have many so called "virtual hosts"
> defined - the same webserver on the same IP address serves many
> websites; it knows which one to serve by the hostname that the client
> (the browser) sends to it.
> Putting 127.0.0.1 in your hosts file and pointing your browser to it is
> a widely used trick to make it connect to a remote site through a
> tunnel; of course, the tunnel must be established first.
> Peter Pentchev roam at ringlet.net roam at FreeBSD.org pp at storpool.com
> PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
> Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
More information about the stunnel-users