Repository navigation
Headers containing commas generate validation errors #114
Description
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.
Activity
mromaszewicz commentedon Mar 19, 2026
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.
Fix regression in binding simple parameters
Fix regression in binding simple parameters (#115)
mromaszewicz commentedon Mar 25, 2026
@jamesfcarter - I've pushed runtime v1.3.1 to address just this issue. Please let me know if it works for you, and reopen this issue if it doesn't.
jamesfcarter commentedon Mar 26, 2026
This does work. Thanks for the speedy response.