Marcel Ludwig

See PR #17 I have added a new field `error` which contains the related err message.

My proposal is to apply user configured headers even on connect errors if applicable. For example: ```hcl set_response_headers = { x-request-id = req.id Cache-Control: no-store ... } ``` This information...

I would apply the ordered list - no magic reordering. Should we reply with some additional headers like https://github.com/sashabaranov/go-openai/blob/master/ratelimit.go#L10 ? This could also be interesting for our BE limiters.

its about the default behaviour which should still be enabled? So the best default boolean is a false one.

Hi, since we use this pkg [@avenga/couper](https://github.com/avenga/couper) and have to ensure backward compatibility we came up to a Gatherer Wrapper. This works with v0.33 and those labels are applied to...