|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Jason,
I made a "lot" of debug session, and I think I may have found the culprit.
With vijava-5.1 the first https request sent to the server contains a header with
"SOAPAction: null".
With Apache 2.2.16 as a proxy server (with mod_rewrite) the server response is "400 Bad Request". This is not the case with apache 2.2.17 and above...
With vijava-5.0, the first request header contains "SOAPAction: 4.0"
Looking at vijava 5.1 source code, in the file com/vmware/vim25/ws/WSClient.java,
the soapAction property is initialized to "null". It should be initialized to
SOAP_ACTION_V55. I tried and it worked.
The vijava project seems to be inactive for months now... I don't know
if it is possible to contact its team.