https://github.com/cetanu/extauthz_request_id_repro
https://github.com/cetanu/extauthz_request_id_repro
Last synced: 8 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/cetanu/extauthz_request_id_repro
- Owner: cetanu
- Created: 2022-01-14T08:48:55.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-01-14T09:38:29.000Z (over 4 years ago)
- Last Synced: 2025-03-16T12:45:28.474Z (over 1 year ago)
- Language: Rust
- Size: 4.25 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Prerequisites
-------------
* Docker
* Docker-compose
* A http client
Steps
-----
The following will stand up a stack that reproduces the issue.
The request made against envoy will cause envoy to check the request
using the configured extauthz service.
The service will print the id, extracted from the httpRequest, and then
allow the request.
Envoy will receive the OK, proxy the request to the httpbin backend, which
will show the request headers that Envoy received (if you used the `/headers` path).
1. `docker-compose up --build extauthz envoy`
2. curl http://localhost/headers