Why does JBossWeb fallback to the default cipher-suite when only unavailable ciphers are requested?
Issue
Why does JBossWeb fallback to the default cipher-suite when only unavailable ciphers are requested? Shouldn't it fail to start or print a warning?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
