Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Errors-To: <wrowe@rowe-clan.net>
Message-Id: <6.2.0.14.2.20041208115354.05a2b6d0@pop3.rowe-clan.net>
Date: Wed, 08 Dec 2004 11:56:10 -0600
To: dev@httpd.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: Testing TLS Upgrade (was: Re: Patch for bug 18757 breaks
  TLS upgrade)
Cc: <dev@httpd.apache.org>
In-Reply-To: <s1b6c502.097@sinclair.provo.novell.com>
References: <s1b6c502.097@sinclair.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:10 AM 12/8/2004, Brad Nicholes wrote:
>  FYI, if anybody else is interesting is testing the TLS upgrade
>functionality, there is a small test utility
>(http://www.apache.org/~bnicholes/tlsupgrade.c) that can be used to send
>an upgradeable GET or POST request.

It seems to me we can make ab.c TLS upgrade-aware by;

  1. recognizing the -s flag in conjunction with http: - that
     would set the ssl preference client-side.  (This would not
     alter the behavior of https:, or of -s without a scheme.)

  2. recognize upgrade-required and promote an http: connection
     to SSL when the server-side demands it.

Sane?

Bill