[Bug]: Adjacent servers using internal Docker container name instead of server name in URLs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 232
- Forks
- 77
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 17
Description
Checked for duplicates
Yes - I've already checked
Describe the bug
I'm running MMGIS in Docker with stac-fastapi-pgstac. I'm having trouble with stac-fastapi respecting the server name
If I hit the STAC catalog with just the IP address, the stac collection uses that IP as the server name in its URLs.
If I use the load balancer address, it uses "http://stac-fastapi/" instead of the server name.
What did you expect?
I expect URLs in STAC results to match the server and path used to make the request.
Reproducible steps
Environment
Contributor guide
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
Reproduce the Docker deployment with stac-fastapi-pgstac, comparing requests made through the IP address and the load balancer address. Trace where STAC result URLs are produced or configured; done means both paths return URLs using the server name and request path rather than http://stac-fastapi/.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, fastapi, javascript
- Domain
- api, backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100