api_prefix doesn't work
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I’ve deployed burrow in k8s. To access it I use ALB burrow.staging.some.domain.com
The configuration file has api_proxy set to “/staging/burrow”
Staging.toml:
[gerenal]
pidfile = ...
access-control-allow-origin = ...
api_prefix = "/staging/burrow"
….
The nginx.conf:
location /staging/burrow {
set $upstream_something http://burrow.staging.some.domain.com;
proxy_pass $upstream_something;
}
What do I expect?
When I run from nginx container
Curl –v http://burrow.staging.some.domain.com/v3/kafka I see http 200 ok
But also I want to see
Curl –v localhost/staging/burrow to see 200 ok as well
But I see 404
Maybe I’ve configured it in wrong place?
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 404 for /staging/burrow using the shown Burrow and nginx configuration, then trace how api_prefix is read and how the request is routed. Done means the prefixed endpoint returns HTTP 200 while the existing /v3/kafka endpoint continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100