Title:
Any reason CF does not preconfigure support of https for axis2 web services?
| View in TrackerStatus/Resolution/Reason: To Fix//EnhancementRequired
Reporter/Name(from Bugbase): Charlie Arehart / ()
Created: 06/30/2018
Components: Web Services, Axis 2
Versions: 2016
Failure Type: Others
Found In Build/Fixed In Build: /
Priority/Frequency: Normal /
Locale/System: /
Vote Count: 0
Ever since CF10 added support for axis2, folks trying to use that with https have found that it failed out of the box. Instead, they have to know to modify CF's axis2.xml file to add an https transportreceiver line. But why should we have to, now 6 years later? Why can't CF do this by default for us?
Is there some reason that turning it on by default is a problem?
Of course, we can ask also if/whether Tomcat itself preconfigures it to be enabled by default, and if not, why not. I have not found any such info (via google searching about that https transportreceiver).
In the meantime, those who may find this and need to enable it manually in CF10 and above, see this blog post:
http://www.shavedmonkeys.com/index.cfm/coldfusion-blog/deploy-ssl-https-webservice-in-coldfusion/
Attachments:
Comments: