Hi Ramesh, One solution is to have separate acceptor ports for HTTP and HTTPS and let the handlers be different which will decide if it is going to use http or https.
Regards, Jana On Wed, Jul 16, 2008 at 11:23 AM, Ramesh Rao <[EMAIL PROTECTED]> wrote: > Hi, > We are using MINA framework in our project to do some custom processing of > HTTP/HTTPS messages which are finally sent > to target Web-Server. > Our MINA is server acts as Proxy Server to the end Web-Server. > We are using a custom protocol to send the HTTP/HTTPS messages. Also the > client is specific to the application, i.e our > client intercepts the browser messages, and wraps it up as custom protocol > message. > After receiving the custom protocol message at MINA Server, we decode using > ProtocolCodecFilter, do some processing and > finally send to the target web-server. > This works well for HTTP messages, as we open the Socket ( Using MINA > Connector interface ) on the target web-server and > send the HTTP message destined to the Web-server. > But for HTTPS messages, we are having issue about how to detect if its > HTTPS message, as we have open up SSL socket ( > default 443 ) on the target web-server and send the request. > I looked at MINA SSLFilter class. But this class supports SSL at MINA > level, i.e if we have do the handshaking, not the > target web-server. > But in our case we want to do some processing on the incoming custom > message, detect if its HTTP or HTTPS and then > accordingly open the correct socket port on the end web-server to send the > request. > Does MINA has a way to detect if its HTTP or HTTPS ( using headers ) when > sending wrapped up HTTP/HTTPS message within a > custom protocol. > Appreciate any help on this issue. > > Thanks, > -- www.vshareride.com www.pragmaticinvesting.com www.younag.com
