Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PUBLIC_SERVER_ADDRESS value can have conflicting requirements #11723

Open
bferguso opened this issue Jan 10, 2025 · 0 comments
Open

PUBLIC_SERVER_ADDRESS value can have conflicting requirements #11723

bferguso opened this issue Jan 10, 2025 · 0 comments

Comments

@bferguso
Copy link
Contributor

The PUBLIC_SERVER_ADDRESS is used to

  1. generate the URL for export download links, and
  2. as a basis for webpack to generate resources.

This can be a problem if:

  1. an application is hosted behind a reverse proxy and
  2. the externally accessible hostname does not resolve from the server

In this circumstance it appears that only one of the uses of PUBLIC_SERVER_ADDRESS can work for any given value.

For example, our implementation has the following external URL (outside of the reverse proxy, which does not resolve from the server):
https://apps.nrs.gov.bc.ca/bcrhp
but the URL necessary for webpack to generate resources is the hostname:
https://<hostname>:port/bcrhp where the hostname is not accessible to the public.

The external URLs for things like download links can be corrected by overriding default Arches Core views/functions however it seems like the URL used by webpack and for URLs generated for external access should be able to be different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant