Trong Huu Nguyen 10e71a7bb5 feat(handler/reverseproxy): remove x-wonderwall headers ...

The use of these headers in upstreams may be risky, espeically
if Wonderwall is accidentally misconfigured or disabled, or requests
are performed directly to the upstream circumventing Wonderwall.

We should prefer using a signed token or similar that can be verified by
the upstreams.

2024-01-16 08:57:07 +01:00

..

config

feat(handler/reverseproxy): add toggle for access logs

2023-12-20 08:25:35 +01:00

cookie

revert: "feat(handler/error): remove automatic retry"

2023-12-20 11:17:51 +01:00

crypto

fix(crypto): set max plaintext size

2023-05-24 12:32:52 +02:00

handler

feat(handler/reverseproxy): remove x-wonderwall headers

2024-01-16 08:57:07 +01:00

ingress

refactor(ingress): simplify and remove unnecessary variables

2023-10-03 14:21:08 +02:00

jwt

feat: log and propagate session metadata

2023-12-19 08:46:02 +01:00

logging

refactor(middleware/logentry): replace zerologger with logrus

2022-07-18 15:47:35 +02:00

metrics

refactor(metrics): minor cleanup

2023-04-29 08:30:08 +02:00

middleware

feat(handler/reverseproxy): remove x-wonderwall headers

2024-01-16 08:57:07 +01:00

mock

refactor(openid): use pkce implementation from golang.org/x/oauth2

2023-10-10 10:18:01 +02:00

openid

feat(handler/login): remove legacy cookie

2023-12-19 08:46:08 +01:00

otel

style: formatting

2023-11-28 10:15:32 +01:00

retry

refactor: use pointer receivers when possible

2022-07-19 19:24:28 +02:00

router

fix(router): skip middleware if otel is not enabled

2023-11-28 10:12:15 +01:00

server

fix(server): correcter error equality check

2023-10-25 10:37:56 +02:00

session

feat(handler/reverseproxy): remove x-wonderwall headers

2024-01-16 08:57:07 +01:00

strings

revert: "style: go fmt"

2023-10-10 14:51:12 +02:00

url

revert: "style: go fmt"

2023-10-10 14:51:12 +02:00