Headers containing commas generate validation errors

[jamesfcarter]

When upgrading to v1.3.0 I started seeing errors like this:

Invalid format for parameter X-My-Header: parameter 'X-My-Header': expected single value, got 24 parts

X-My-Header was a JSON string containing commas.

This appears to be due to the headers now being run through splitStyledParameter which splits on comma and requires only one part. (#100)
I've worked around this by using a type that implements encoding.TextUnmarshaler to avoid it reaching that code but was this behaviour intended?

Thanks.

[mromaszewicz]

No, it wasn't intended. Thanks for reporting.

I'll add test cases for this and fix it. It's difficult to infer intent from looking at data without context, so I've been fixing these bugs by passing down more context from higher levels.