-
1. Why JBR-listener, designed as HTTPS really work througth HTTP protocol?
tcunning Apr 29, 2011 12:17 PM (in response to gdr)When you say you "I see that jbr-listener available through http protocol and not available through https protocol" - what exactly are you looking at?
Are there possibly network differences (firewall, etc) between your development environment and the production server?
-
2. Re: Why JBR-listener, designed as HTTPS really work througth HTTP protocol?
gdr Apr 29, 2011 2:15 PM (in response to tcunning)I open my browser and type: https://localhost:3536 and browser tell me that this url is invalid, then i type url http://localhost:3536 and browser show me call stack (call stack in this situation is normal, because my service handles only POST queries, not GET). On my dev server I see the same call stack when I use https://localhost:3536 url.
But, in http://localhost:8080/contract I see, that wsdl of my service available at url http://localhost:8080/contract/contract.jsp?serviceCat=SWS&serviceName=SecureWebService&protocol=https, and this url works.
-
3. Why JBR-listener, designed as HTTPS really work througth HTTP protocol?
gdr May 10, 2011 7:38 AM (in response to tcunning)Now I check the traffic by fiddler. It is really unencrypted HTTP traffic.
I was try to use standard configuration and configuration with binding manager - the same results (HTTPS works at development server and doesn't works at production).
What I should check more?
-
4. Re: Why JBR-listener, designed as HTTPS really work througth HTTP protocol?
tfennelly May 11, 2011 5:49 AM (in response to gdr)This sounds really odd for sure. If it were me I'd be wonering am I looking at or deploying to the same server. Your app is configured for https, yet after deployment you have http (not just a broken https). That sounds like magic
Anyway... I think you should consider using the http gateway: http://community.jboss.org/wiki/HTTPGateway
-
5. Re: Why JBR-listener, designed as HTTPS really work througth HTTP protocol?
gdr May 12, 2011 9:25 AM (in response to gdr)I didn't understand the cause of problem, but I solve it: I just install JBoss ESB on JBoss AS 5.1. Before it I used the standalone version of JBossESB