We use BigIP to perform SSL duties for our website. We are about to add a filter to force all page accesses to be sure.
The plan is to have two ports (9000 for regular requests and 11000 for secure requests). It would work like this: Request comes in on port 80 to BigIP. It would send the request to port 9000 on the tomcat. The filter would check the scheme. It is not https, so it would redirect to the same URL with the scheme of https. BigIP would receive the redirected request on port 443. It would decrypt it and send it to port 11000. I see where it has the scheme and secure parameters on the standard connector. I was thinking that I could use a regular connector, but change scheme to https. This would give my filter what it needs and still allow BigIP to perform decryption. However, when I do this, requests to https (443) hang. They never get through. Any ideas? ===== Norris Shelton Software Engineer Sun Certified Java 1.1 Programmer Appriss, Inc. ICQ# 26487421 AIM NorrisEShelton YIM norrisshelton __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
