You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Header values are URI-encoded by swift-openapi-generator. This is incorrect eg. for Cache-Control headers where translating max-cache=3600 to max-cache%3D3600 produces an invalid cache-control header.
Yeah this is a bug. In earlier OpenAPI spec versions, it was implied that headers should be percent-encoded. And then recently, in 3.2.0, they clarified that they shouldn't. So we'll need to find a way to gently switch that behavior while breaking the fewest existing adopters.
TBD what the process will be, ideas welcome.
The fix will be in swift-openapi-runtime, and we want new adopters to use it, so the obvious solutions like a flag in openapi-runtime-config.yaml wouldn't work very well.
Activity
czechboy0 commentedon Jan 8, 2026
Yeah this is a bug. In earlier OpenAPI spec versions, it was implied that headers should be percent-encoded. And then recently, in 3.2.0, they clarified that they shouldn't. So we'll need to find a way to gently switch that behavior while breaking the fewest existing adopters.
TBD what the process will be, ideas welcome.
The fix will be in swift-openapi-runtime, and we want new adopters to use it, so the obvious solutions like a flag in openapi-runtime-config.yaml wouldn't work very well.