I met with the Cisco developers that frequent this list today, and one of the things we discussed was HTTP vs HTTPS. I'm sharing these thoughts here for the benefit of other users:
The team determined that having http:// in the EPR address should not be a problem for secure messages because the WS-A headers are part of the SOAP envelope and not used by the HTTP/SOAP server for routing. Tomcat will route an https:// request to the right application, it will go through Axis2, and then Muse, where the WS-A headers (with a http:// address) will be processed. This is valid because WS-A headers are really about identifying the resource and not the type of transport used to talk to it. The team will report back if they have any problems getting Axis2 to accept requests with HTTPS transport but HTTP URIs in the WS-A Address (since Axis2 analyzes the WS-A headers during request processing). Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 02/06/2007 02:19:35 PM: > Does Muse have support for SSL? At the least, it would be nice to have > an easy way to update the URI in an EPR to have the prefix "https" > instead of "http". I'm not sure if it's easier for me to create the > util, or to have it in Muse. I would assume the rest of the work isn't > in Muse's domain? We have two scenarios: > > 1) SSL is used directly between the client and the server hosting the > Muse app. So the client must connect using "https", and the app must > return an EPR containing "https". > 2) SSL is used between the client and the webserver, but is not used > between the webserver and the app server hosting the Muse app. So the > app will never return "https", but the webserver has the responsibility > for converting to "https" to the client, and to back to "http" from the > client. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
