You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my example, I am proxying a GetLegendGraphic request from MapCache to a backend WMS service.
However the tileset name in Mapcache is different than the Layer name in Mapserver.
In this example, the Mapcache tileset name is "Brisbane" and the corresponding Mapserver layer name is "HiResBNEColoured".
I can set up a forwarding rule that looks like this:
So Mapserver gets two values for LAYER, with the proxied one appearing after the given on the URL parameter, and it seems Mapserver chooses the one which appears last, so it returns a "Layer not found" error.
Solution: It would be ideal to allow the forwarding rule to be configured to modify proxied parameters according to some given rules.
For example, this would be great:
In my example, I am proxying a GetLegendGraphic request from MapCache to a backend WMS service.
However the tileset name in Mapcache is different than the Layer name in Mapserver.
In this example, the Mapcache tileset name is "Brisbane" and the corresponding Mapserver layer name is "HiResBNEColoured".
I can set up a forwarding rule that looks like this:
However this doesn't work, because mapcache appends all parameters to the proxied request, so Mapserver receives a request that looks like this:
So Mapserver gets two values for LAYER, with the proxied one appearing after the given on the URL parameter, and it seems Mapserver chooses the one which appears last, so it returns a "Layer not found" error.
Solution: It would be ideal to allow the forwarding rule to be configured to modify proxied parameters according to some given rules.
For example, this would be great:
The text was updated successfully, but these errors were encountered: