Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v730)
In-Reply-To: <42CAC65E.1050909@force-elite.com>
References: <3891F9F6-A04B-44ED-BA3D-AD5EA3E97577@jaguNET.com>
 <42CAC65E.1050909@force-elite.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F54F6A46-30BE-46F4-AB28-044EACECC240@jaguNET.com>
Content-Transfer-Encoding: 7bit
From: Jim Jagielski <jim@jaguNET.com>
Subject: Re: [PATCH] Allow for internal OpenSSL Session Cache
Date: Tue, 5 Jul 2005 13:55:40 -0400
To: dev@httpd.apache.org


On Jul 5, 2005, at 1:41 PM, Paul Querna wrote:

> Jim Jagielski wrote:
>
>
>> I've run into this with some "broken" browsers. Basically, they
>> require a non-null SessionID in the SSL transaction. If, for whatever
>> reason, we disable the external SSL Session Cache, these
>> browsers reports errors when connecting to the SSL vhost.
>>
>> This adds a new argument to SSLSessionCache which says "disable any
>> external session cache, but use OpenSSL's internal one" which makes
>> OpenSSL send the SessionID parameter again.
>>
>>
>
> How about "internal" instead of "justinternal"?
>

Yeah, I'm not too happy with 'justinternal'... but a shared memory cache
could be considered "internal"... How about "nonshared" or "openssl"
or whatever :)

> I assume this session cache is local to the SSL Context?
>
> Any browser which requires an SSL Session to work is quite broken.   
> Do you have a list of browsers that we could add to the documentation?

Mostly seen in, no surprise, some MSIE browsers, as well as some Java
HTTPS clients. I'll try to get the list.