Closed JackMcKew closed 6 months ago
Hey! Any chance this is because of that botched SRID in the provider config?
The underscores in the SRID don't make a difference
today I learned it also is supported in toml
Let me go ahead and try to reproduce the issue
update:
yup, reproducible. However, this "only" affects the viewer. Tiles are served correctly at:
http://localhost:8080/public/map-tile-server-tegola/maps/map_tiles/{z}/{x}/{y}.pbf
I don't really see why this would happen, as the viewer endpoints are attached to the same group as all the other endpoints.
Ah awesome, at least the tiles are still being served correctly, was throwing me down all sorts of rabbit holes
I'll leave this issue open as it definitely affected me
@iwpnd did you find the root cause of this issue? I will need to look through the commit log to figure out when this change occurred.
i did not go down the rabbithole just yet, nope
update:
while you can point the http.FS
of the built viewer to whatever uri_prefix
you like, the vuejs app itself is using /
as apiRoot
. So when the app is starting and trying to collect information from /capabilities
although your capabilities are at /my_prefix/capabilities
, the catch statement is printing the resulting 404. So I think this is an issue with the vuejs app, rather than tegola server.
I've been recently trying to upgrade from version
0.13.0
to0.16.0
. My use case depends on the uri_prefix because I'm using a proxy via an ingress in Kubernetes.My config looks like
When I spin this up locally using the following Dockerfile:
On versions
0.13.0+
, I can reachlocalhost/public/map-tile-server-tegola/capabilities
, the json returns as expected. However, if I head tolocalhost/public/map-tile-server-tegola
, all I see is 404 responses.On version 0.13.0, this shows the viewer as expected.
Let me know if you can't reproduce this issue