Inconsistent / Incomplete handling of CONFIDENTIAL transport-guarantee defined in jboss.xml compared to @WebContext annotation ------------------------------------------------------------------------------------------------------------------------------ Key: JBWS-2943 URL: https://jira.jboss.org/jira/browse/JBWS-2943 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.Beta4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3 If the transport-guarantee is set to CONFIDENTIAL using the @WebContext annotation then the following happens: - 1 - The services page https://localhost:8443/jbossws/services lists access to the WSDL using a https address. 2 - The address in the WSDL is a https address. (Regardless of if WSDL is accessed over http or https) 3 - The endpoint called over http results in a 302 status being returned. If the transport-guarantee is defined in the jboss.xml then only the following happens: - 3 - The endpoint called over http results in a 302 status being returned. The first two report only http addresses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira