On 04/29/2014 06:03 AM, Amos Jeffries wrote:
> I'm fine with "transferProtocol" or just "protocol" (although that may
> get as common as "conn" has become). Whichever suits you.
Let's avoid "protocol" for the reasons you mentioned and use
"transferProtocol".
>>> This variable can
>>> be altered
On 29/04/2014 9:12 a.m., Alex Rousskov wrote:
> On 04/28/2014 07:10 AM, Amos Jeffries wrote:
>
>> * ssl-bump transforms the transportVersion from whatever it was
>> previously (usually HTTP or HTTPS) to HTTPS.
>
>> +/// the transport protocol currently being spoken on this connection
>> +
On 04/28/2014 07:10 AM, Amos Jeffries wrote:
> * ssl-bump transforms the transportVersion from whatever it was
> previously (usually HTTP or HTTPS) to HTTPS.
> +/// the transport protocol currently being spoken on this connection
> +AnyP::ProtocolVersion transportVersion;
If I recall ou
We are quickly approaching a time when a client connection can freely
migrate between protocols or versions of protocols. Already we have
ssl-bump which can switch a connection from HTTP to HTTPS. I am
expecting switching HTTP<->HTTPS via Upgrade, and HTTP/1<->HTTP/2 via
"magic", Upgrade, or ALPN.
