]> git.ipfire.org Git - thirdparty/squid.git/commit
Replaced PROTO_SSL_PEEK with request_flags::sslPeek and disabled server SNI
authorAlex Rousskov <rousskov@measurement-factory.com>
Wed, 1 Feb 2012 05:13:24 +0000 (22:13 -0700)
committerAlex Rousskov <rousskov@measurement-factory.com>
Wed, 1 Feb 2012 05:13:24 +0000 (22:13 -0700)
commit2c065fc8a4f92da5702c5273e937e6442e1f678e
treed6d7ca2a5fc4ca0d7bd0f48fff7e684b3d0eb982
parentc9ecfe8ad94a7be1bfe483705563254cd5606d78
Replaced PROTO_SSL_PEEK with request_flags::sslPeek and disabled server SNI
for bump-server-first connections.

While PROTO_SSL_PEEK was a safer design option because requests with the
"wrong" protocol scheme would be less likely to leave Squid, it required
all error-generation code to replace the protocol with PROTO_HTTPS so
that error make more sense to end users. We no longer have to do that.

The server-side SNI for bump-server-first connections has to be disabled
because bump-server-first code does not yet know the true intended server name
(even for those CONNECT requests that have server name, it would be a little
risky to use CONNECT info for SNI). That name could be eventually obtained
from the client before we peek at the server certificate but that work
is outside this project scope.
src/anyp/ProtocolType.h
src/forward.cc
src/forward.h
src/ssl/ServerPeeker.cc
src/structs.h