A couple options:
- Use absolute paths (to a network share or fast disk or where your actual
data lives)
- Experiment with "geosever-environment.properties" as outlined here
<"https://docs.geoserver.org/latest/en/user/community/backuprestore/configtemplate.html>
to
avoid typing in the same
Hi Paul,
as far as I know, the plugin does not do any internal caching.
However, it sets an HTTP header so that the client would do some caching of
the response, see:
On Mon, Oct 5, 2020 at 1:43 PM Nicolas De Ville de Goyet <
ndevi...@naturalsciences.be> wrote:
> So I'm a bit confuse at where I should fix the problem... I'm downloading
> directly on geoserver so it should understand the URL encoding?!
>
My guess is that the proxy is url-encoding again the
Hello Andrea,
Thanks for your reply.
The error arise when I'm in the Layer preview page on geoserver itself.
The url is this one: https://spatial.naturalsciences.be/geoserver/web/
To reproduce the error, search the layer borehole. Then download the gml
preview (max 50 features):
On Mon, Oct 5, 2020 at 12:31 PM Nicolas De Ville de Goyet <
ndevi...@naturalsciences.be> wrote:
> My problem is that the proxy translates the 'special' characters in
> hexadecimal form in the GetFeature request (i.e.: workspace:feature -->
> workspace%3Afeature) and geoserver is not able to
Hello everyone,
I'm struggling with GetFeature requests to geoserver behind a proxy.
I followed the instructions here and modified the web.xml document to
allow the redirection:
/https://docs.geoserver.org/latest/en/user/security/webadmin/csrf.html/
My problem is that the proxy translates
