We have jBPM 5.4.0 running behind Apache httpd via AJP, and have configured jBPM to route through Apache's SSL interface. This works fine for accessing /drools-guvnor and /jbpm-console. However, trying to start a workflow process yields the following error in the browser:
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Hint: https://<FQDN>/
It seems that some component of jBPM or JBoss is sending out non-SSL data. What is the best way to pinpoint where this is coming from and discern how to reconfigure for proper SSL output?