Without looking at the code.... The pound server would need the private key to 
"impersonate" the client's cert.... So I don't think your second option is 
possible.

However all the HTTP/SSL headers pound inserts should apply to both HTTP and 
HTTPS backends.

Joe


> -----Original Message-----
> From: Rob Moore [mailto:[email protected]]
> Sent: Friday, September 24, 2010 10:23 AM
> To: pound
> Subject: [Pound Mailing List] Client certs and HTTPS Backends
>
> I couldn't find any documentation on this in the latest man page or on
> the
> list so thought I'd ask.
>
> Is the client certificate passed via HTTP headers to the HTTPS backend
> (just
> as it would be to an HTTP backend) or is it used directly in the
> request to
> the HTTPS backend (as it would be if the browser connected directly to
> the
> backend without Pound)? I'm assuming the former but wanted to confirm.
>
> Thanks,
>
> Rob
>
>
> --
> To unsubscribe send an email with subject unsubscribe to
> [email protected].
> Please contact [email protected] for questions.

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to