DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38524>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38524 ------- Additional Comments From [EMAIL PROTECTED] 2006-05-23 09:46 ------- >From mod_proxy_http.c Apache 2.2.2 /* * TODO: Currently we cannot handle persistent SSL backend connections, * because we recreate backend->connection for each request and thus * try to initialize an already existing SSL connection. This does * not work. */ if (is_ssl) backend->close_on_recycle = 1; (In reply to comment #12) > We were experiencing the same problem for our reverse proxy (v2.0) and > therefore > updated to version 2.2.2 that included this patch. > For testing and debugging purposes we used HTTP connections to our backend (a > webdispatcher). > Client <--https--> Apache2.2.2 as Reverse Proxy <--http--> Dispatcher > <--http--> > App Server > > For production we need a HTTPS connection to this webdispatcher. > Client <--https--> Apache2.2.2 as Reverse Proxy <--httpS--> Dispatcher > <--http--> App Server > > When using this setup (mod_proxy + mod_ssl), we're experiencing a lot more > connections in contrast to the setup without mod_ssl. > Since I cannot sniff on these HTTPS connections, I cannot provide you with any logs. > > Has anyone experienced the same problem? Any suggestions? (In reply to comment #12) > We were experiencing the same problem for our reverse proxy (v2.0) and > therefore > updated to version 2.2.2 that included this patch. > For testing and debugging purposes we used HTTP connections to our backend (a > webdispatcher). > Client <--https--> Apache2.2.2 as Reverse Proxy <--http--> Dispatcher > <--http--> > App Server > > For production we need a HTTPS connection to this webdispatcher. > Client <--https--> Apache2.2.2 as Reverse Proxy <--httpS--> Dispatcher > <--http--> App Server > > When using this setup (mod_proxy + mod_ssl), we're experiencing a lot more > connections in contrast to the setup without mod_ssl. > Since I cannot sniff on these HTTPS connections, I cannot provide you with any logs. > > Has anyone experienced the same problem? Any suggestions? (In reply to comment #12) > We were experiencing the same problem for our reverse proxy (v2.0) and > therefore > updated to version 2.2.2 that included this patch. > For testing and debugging purposes we used HTTP connections to our backend (a > webdispatcher). > Client <--https--> Apache2.2.2 as Reverse Proxy <--http--> Dispatcher > <--http--> > App Server > > For production we need a HTTPS connection to this webdispatcher. > Client <--https--> Apache2.2.2 as Reverse Proxy <--httpS--> Dispatcher > <--http--> App Server > > When using this setup (mod_proxy + mod_ssl), we're experiencing a lot more > connections in contrast to the setup without mod_ssl. > Since I cannot sniff on these HTTPS connections, I cannot provide you with any logs. > > Has anyone experienced the same problem? Any suggestions? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
