Hi Mark,
> Ricardo Wurmus <rek...@elephly.net> writes: > […] >> The reason why it fails is that Guile processes the response and treats >> the *payload* contained in the XML response as HTTP. > > No, this was a good guess, but it's not actually the problem. You are right. I also ended up trying with “wget --save-headers” after sending the bug report and noticed the offending header like you did: > Content-Type: multipart/related; type="text/xml"; start="<main_envelope>"; > boundary="=-=-=" > > <?xml [...] I assumed it was part of the payload when it really was a regular header after all. > The problem is simply that our Content-Type header parser is broken. > It's very simplistic and merely splits the string wherever ';' is found, > and then checks to make sure there's only one '=' in each parameter, > without taking into account that quoted strings in the parameters might > include those characters. Right. I worked around this in guile-debbugs simply by replacing the Content-Type header parser with one that lacks the check for the unique “=” in the string part. > I'll work on a proper parser for Content-Type headers. Thanks! -- Ricardo