AWS + ECP?

[Cantor, Scott]

> Thanks. Maybe Brent has an obvious insight, but I haven't figured out why
> our decoding logic would be behaving that way in this situation. I don't know
> if we even look at Content-Type, and if we did, we'd have a clear error. All I
> see is the code passing the request stream from the servlet into the XML
> parser. I don't understand how that causes that error on both containers yet.
> It's very odd.

We probably figured this out months ago, the problem is just the script and use of curl, it defaults the Content Type to form-encoded if you don't set it.

I can speculate your AWS issue might be that, but you'd have to sniff it.

-- Scott