-
Notifications
You must be signed in to change notification settings - Fork 10
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
ProxyPass with externalURL setting does not work for subfolders #94
Comments
So do I understand correctly that this cannot be modified within the
configuration?
Also - are the 2 subpaths I set (manager and rest) all, or must I set
additional ones? If I don't do this on the subpath level, I cannot run
any other services on this server!
…On 02.03.2018 15:18, Andreas Zahnen wrote:
ldproxy needs to know the URL it will be accessed with, so if proxying
it e.g. with apache httpd or nginx, the externalURL parameter has to
be set. This works as long as ldproxy is still available in the root
folder, but not when it is in a subfolder like
|http://localhost/ldproxy/|.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#94>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/ALXQKBKJTZXa89SLSxG4VjKFV2X2vWICks5taVSagaJpZM4SZ9CX>.
--
_________________________________________________________________________
Katharina Schleidt
Tel: +43 (1) 89 234 26
Mobile: +43 (650) 89 234 26
Skype: Kathi Schleidt
Kathi@Schleidt.org
www.schleidt.org/kathi
In the twenty-first century censorship works by flooding people with irrelevant information.
-- Homo Deus, Yuval Noah Harari
The people can always be brought to the bidding of the leaders.
That is easy. All you have to do is tell them they are being attacked
and denounce the pacifists for lack of patriotism and exposing the country to danger.
It works the same way in any country.
--Hermann Göring, Nazi military leader (12 Jan 1893-1946)
|
Code has been rewritten for the 2.0 release. The external URL can be set in the configuration, we will document this in the documentation update for version 2.0. |
We have a similar situation: ldproxy gives 404 behind a subpath, even with
The above setup works for other deployed services like pygeoapi. There we need to set How can we solve this with the current versions of |
Working! Doing a similar thing in See our new config here. Maybe this is something for the ldproxy documentation, as Traefik is used extensively. |
Thanks @justb4. We are also using Traefik in the xyz.ldproxy.net deployments, but then always without a path. We will have a look, how we can update/improve the documentation. I think there might still an issue that we need to address, because the css link does not work. |
@justb4 ReplacePath is not the right tool for this case, it will replace any path with the static path
For simpler cases without subpath we use the AddPrefix middleware:
|
@azahnen thanks. I tried your suggestion within Geonovum/ogc-api-testbed#6, and several variants, but no success. Aim is to run When trying your suggestion, still Our Docker compose file with the Traefik config. We did get services behind Traefik working for |
@justb4 Sorry, that was just a theoretical example and obviously it does not work. I set up the example in my environment, here is a minimal working
|
Thanks @azahnen , your suggestion works on localhost. A WFS provider has been configured, collections can be navigated, logs look good, ignoring some layer-errors:
But on the server the Traefik path middelware works, but cannot get through the WFS Collection. Logs:
Somehow the WFS Resource is not processed and https://oapi.map5.nl/ldproxy/RCE_Landschapsatlas_WFS gives 404 (the localhost version works). Configuration is identical, in GitHub. Could it be permission problems ? We had permission problems, container changing file-ownership, with GeoServer. Also I tried the same convention to access the manager on localhost via
|
@justb4 It looks like you figured out the 404 issue, as I can access https://apitestbed.geonovum.nl/ldproxy/RCE_Landschapsatlas_WFS. The manager needs some rest endpoints relative to the manager path, so one more RegexReplace is needed. For example this works for me, manager runs at http://localhost:8080/ldproxy/manager/:
|
@azahnen thanks again. Yes, somehow the endpoint https://apitestbed.geonovum.nl/ldproxy/RCE_Landschapsatlas_WFS suddenly worked. Ok, took the latest We found another issue when opening the OAS Swagger page, see: |
ldproxy needs to know the URL it will be accessed with, so if proxying it e.g. with apache httpd or nginx, the externalURL parameter has to be set. This works as long as ldproxy is still available in the root folder, but not when it is in a subfolder like
http://localhost/ldproxy/
.The text was updated successfully, but these errors were encountered: