Skip to content

Serving content from root domain breaks static assets #1477

@balasankarc

Description

@balasankarc

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?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions