On Mon, Apr 21, 2014 at 12:38 PM, Graham Leggett wrote:
> Hi all,
>
> Right now, we have the SSLUserName directive, which takes an arbitrary SSL
> variable and turns it into a username for the benefit of the request. This
> has the downside that only SSL variables (and some CGI variables) are us
On 04/22/2014 08:57 AM, Ligade, Shailesh [USA] wrote:
> I think by default, the certificate hint list asks for client authentication
> certificates. Is there any configuration option to ask for different types of
> certificates? e.g. signing or encryption certificates?
In TLS, the client's secr
I've been working on the SIP over TLS and SIP over WebSockets (with TLS)
in reSIProcate and I'm looking at ways to make it easier people to use
both HTTPS and SIP(S) on a single IP/port
There are already methods (e.g. sshttp) that allow SSH and HTTPS on the
same port - this works fairly easily w
Hi,
the comment is wrong.
'ap_sub_req_lookup_dirent' uses the fact that 'rnew->uri' has some extra
space after the NUL.
'rnew->uri' is allocated via 'ap_escape_uri' which is defined as:
#define ap_escape_uri(ppool,path) ap_os_escape_path(ppool,path,1)
So, what matters here is the case in
