Serving content from root domain breaks static assets
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Version
pulp-operator 1.0.1
Describe the bug
When setting content_path_prefix to '"/"' to serve content from the root domain, the /assets path gets incorrectly sent to the content pod, which does not know how to serve them. This results in broken CSS in the API index page.
To Reproduce
Deploy an instance with content_path_prefix set to '"/"'
Expected behavior
API index page works as expected
Additional context
Should static assets be served from api_root instead of the global root? So that everything required for API UI is scoped under the api_root?
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
No source file or test is named. Start by deploying pulp-operator 1.0.1 with content_path_prefix set to "/" and inspect how the /assets request is routed relative to api_root; done means the API index page loads with its static CSS while content remains served from the root domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100