[GLASSFISH-19293] Acessing EJB based WebService over https with transport-guarantee NONE fails Created: 06/Nov/12  Updated: 11/Feb/13  Resolved: 11/Feb/13

Status: Resolved
Project: glassfish
Component/s: web_services
Affects Version/s: 3.1.2_b05
Fix Version/s: 4.0_b75

Type: Bug Priority: Major
Reporter: stef_esrf Assignee: Lukas Jungmann
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
Linux version 2.6.32-100.26.2.el5 (mockbuild@ca-build10.us.oracle.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Jan 18 20:11:49 EST 2011


Attachments: File UnsecureEAR.ear     Java Source File UnsecureService.java    
Tags: webservice

 Description   

WS deployed as EJB and configured with transport-guarantee NONE can be accessed over http but NOT over https. Seems to be linked to former bug GLASSFISH-5621.

This works fine for web applications (jsp). In our case it is important since all external calls come over https through the firewall, apache and mod_jk to our WS, but all local calls contact the WS directly over http.

Please find a test case attached. Accessing the wsdl under http://<myserver>:8080/UnsecureServiceService/UnsecureService?wsdl works fine. If I try https://<myserver>:8181/UnsecureServiceService/UnsecureService?wsdl I get a blank page and the following error in server.log:

[#|2012-11-06T10:57:08.156+0100|WARNING|glassfish3.1.2|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=424;_ThreadName=Thread-2;|Invalid request scheme for Endpoint UnsecureService. Expected http . Received https|#]

Thanks!



 Comments   
Comment by Lukas Jungmann [ 11/Feb/13 ]

http://java.net/projects/glassfish/sources/svn/revision/59356

Generated at Mon Aug 03 19:21:11 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.