Description of problem: more info can be found at https://bugzilla.redhat.com/show_bug.cgi?id=845832#c30
From the comments in bug 845832 it is not clear to me if this is really needed, but if it is I think this change can be the solution: http://gerrit.ovirt.org/7399
this change is 'must' to allow clients using 'Expect' header (including our sdk)
I trust you.
The proposed change has been merged upstream: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=a441804b8b326d556dc1df9635548ee9ca494aa9
*** Bug 979737 has been marked as a duplicate of this bug. ***
looks like regression was caused by the [1]. [1] http://gerrit.ovirt.org/#/c/13318/
Just for the record, yet another reason why not to use Expect in applications. From the RFC[1] """ The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy MUST return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect request-header itself is end-to-end; it MUST be forwarded if the request is forwarded. """ This means that Expect will not work when using http proxy, and this use case should be valid when accessing the api as ell. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
regression (that previous bug solution caused) was solved in is7.
Closing - RHEV 3.3 Released