Rajneesh ChaudharyandGitHub 54bab503b4 confighttp: add ExposedHeaders to CORSConfig (#15119) ...

`CORSConfig` maps `AllowedOrigins`, `AllowedHeaders`, and `MaxAge` into
`cors.Options`, but doesn't map `ExposedHeaders` even though `rs/cors`
supports it. This means there's no way to set
`Access-Control-Expose-Headers` through receiver config — anyone who
needs it has to write a custom middleware.

This came up in jaegertracing/jaeger#8128 where the Jaeger UI needs
specific headers exposed over CORS but has to work around this gap with
a hand-rolled middleware.

### Changes
- Add `ExposedHeaders []string` to `CORSConfig`
- Wire it into `cors.Options` in `ToServer()`
- Add test
- Update README

Signed-off-by: Rajneesh Chaudhary <[email protected]>

2026-06-01 21:30:33 +00:00

..

ca.crt

add go 1.19 to tests (#5791)

2022-08-03 09:55:10 -07:00

client.crt

add go 1.19 to tests (#5791)

2022-08-03 09:55:10 -07:00

client.key

add go 1.19 to tests (#5791)

2022-08-03 09:55:10 -07:00

config.yaml

confighttp: add ExposedHeaders to CORSConfig (#15119)

2026-06-01 21:30:33 +00:00

middlewares.yaml

confighttp: add support for binding unix sockets (#14248)

2026-01-14 11:54:55 +00:00

server.crt

add go 1.19 to tests (#5791)

2022-08-03 09:55:10 -07:00

server.key

add go 1.19 to tests (#5791)

2022-08-03 09:55:10 -07:00