On 12/15/2017 08:50 AM, Mark Prins wrote:
Broken isn't a very well defined state, it's quite a valid use case to
have (valid ofcourse) urls pointing all over the place.
Fair enough.:)
wrt following redirects; as geotools is still on an old version of
apache httpclient which doesn't provide
2017-12-13 6:02 GMT+01:00 Jim Hughes :
> Hi all,
>
> So I'm slow on the uptake tonight... In the event that the remote server
> is a GeoServer, then the Global settings proxy base url (
> http://docs.geoserver.org/latest/en/user/configuration/glob
> alsettings.html#proxy-base-url) can be set to s
Hi all,
So I'm slow on the uptake tonight... In the event that the remote
server is a GeoServer, then the Global settings proxy base url
(http://docs.geoserver.org/latest/en/user/configuration/globalsettings.html#proxy-base-url)
can be set to sort this issue out.
I suppose it might still be
Hi all,
And to answer my own question... the incorrect URL is coming from the
GetCapabilities document. Basically, I'm getting screwed by a proxy in
the way.
One solution may be for the WFS-NG datastore to follow re-directs in the
HTTP code. Would that be sensible?
Other than that, this
Hi all,
Today I tried out the WFS-NG DataStore with a GeoServer configured with
HTTPS, and I hit two issues. I'll start with the one where I could use
some help...
I passed a url of the form https://hostname/geoserver/..., and after
connecting correctly (using a username and password), subs
