juju bootstrap fails with vSphere 6.0

[Forstner Michael]

Hi Martin,

Very good point - thank you so much for pointing this out!
I’ve did another test drive and actually (at least to me) it looks like the HTTP header for this gzipped response is wrong. The first 3 response headers are indicating that content may gzipped and this malformed 4th response is just indicating that it is content-type XML:

First 3 response headers:

Content-Type: text/xml; charset=utf-8
Vary: Accept-Encoding
Content-Encoding: gzip


4th response header:

Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked


So it seems like I have to file a bug report at VMWare regarding their SOAP API in vSphere6 right?

Thanks and regards,
Michael




On 06.11.15, 10:10, "Martin Packman" <martin.packman at canonical.com> wrote:

>On 05/11/2015, Forstner Michael <Michael.Forstner at cpg.de> wrote:
>>
>> Response 4 (Invalid XML; attaching Hex view):
>> 00000000  1f 8b 08
>
>Aha, that's just gzip encoded. Once decoded, the response looks sane:
>
>http://paste.debian.net/325311
>
>So, need the http headers as well. If the vSphere server included
>"Content-Encoding: gzip" response header then the client can certainly
>unpack it, whether or not an Accept-Encoding request header was given.
>
>Martin