We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No description provided.
The text was updated successfully, but these errors were encountered:
Sample Layman configuration for running at specific URL prefix. Just for make start-demo (without Micka and Liferay).
make start-demo
URLs in GET Layer|Map response will be probably wrong (probably https://local.examples/rest/... instad of https://local.examples/layman/rest/...)
https://local.examples/rest/...
https://local.examples/layman/rest/...
https://local.examples/layman
... server { listen 80; server_name local.examples; client_max_body_size 2m; ... location /layman/ { proxy_set_header Host $host:$server_port; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http://127.0.0.1:8000/layman/; #8000 } }
docker-compose.demo.yml
... nginx: ... ports: - 8000:80 ...
LAYMAN_GS_PROXY_BASE_URL=https://local.examples/layman/geoserver LAYMAN_PROXY_SERVER_NAME=local.examples LAYMAN_CLIENT_URL=http://layman_client:3000/layman/client/ LAYMAN_CLIENT_PUBLIC_URL=https://local.examples/layman/client/ LTC_BASEPATH=/layman/client CSW_*=... OAUTH2_*=...
Sorry, something went wrong.
Similar behaviour could be achieved with X-Fowarded HTTP headers (#868)
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: