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

WPS hostname not replaced in XML response when behind server proxy #83

Closed
fmigneault opened this issue Mar 3, 2020 · 0 comments · Fixed by #417
Closed

WPS hostname not replaced in XML response when behind server proxy #83

fmigneault opened this issue Mar 3, 2020 · 0 comments · Fixed by #417
Labels
process/wps1 Issue related to WPS 1.x processes support process/wps2 Issue related to WPS 2.x processes support triage/bug Something isn't working triage/enhancement New feature or request

Comments

@fmigneault
Copy link
Collaborator

For example, calling :
${SERVER_HOSTNAME}/ows/wps?request=GetCapabilities&service=WPS

The returned XML document will have https://localhost:4000 in place of ${SERVER_HOSTNAME} instead of the actual server hostname, as defined by weaver.url configuration parameter.

@fmigneault fmigneault added triage/bug Something isn't working triage/enhancement New feature or request process/wps1 Issue related to WPS 1.x processes support process/wps2 Issue related to WPS 2.x processes support labels Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process/wps1 Issue related to WPS 1.x processes support process/wps2 Issue related to WPS 2.x processes support triage/bug Something isn't working triage/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant