Errors that you posted were from proxy server that couldn't connect to the backend, so: 1. It would be good to check log files on backend whatever it is. 2.. Also it would be a good idea to install browser ot the proxy server (or connect computer with browser to that network) and check direct connection to the backend server using client certificate configured on the browser. Everything (your log files and your description of the problem) shows that the problem is between proxy and backend so try to debug that part more deeply. On 12/25/06, Shai Yallin <shai@xxxxxxxxxxxxxx> wrote:
Yeah, but if I try GETting from the proxied server from the proxy using a browser, and display the client certificate, the request succeeds. Please notice that in the log I've posted earlier, it appears that some unexpected error occurs, not an error with a known code, such as "invalid certificate". The request just dies unexpectedly... > If it used to work and now doesn't most probably that there is an > expired certificate somewhere. It could be client certificate that > proxy uses to authenticate on the backend server or root CA's > certificate that signed that client's certificate. Shai Yallin IT Manager & Developer LocatioNet Systems Ltd. Tel: +972-9-8856451 Fax: +972-9-8856452 Mobile: +972-54-4840868 "...we will be restoring normality just as soon as we are sure what is normal anyway."
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|