Yes, we have proxy base URL set. It works fine for say creating the openlayers
preview URL (making it the proxied version). But the preview page itself is
using http instead of https to import the js.
If I get the preview up, I can hack the URL to the unproxied version (which is
http) and then
>From a quick glance it looks to be handled in the base FilterToSQL
writeLiteral function (
https://github.com/geotools/geotools/blob/master/modules/library/jdbc/src/main/java/org/geotools/data/jdbc/FilterToSQL.java#L1512)
it would need the SQLServerFilterToSQL to add an exception to it's write
Hi list.
I've been looking into the limitations of using the field types "bit" (boolean)
and "uniqueidentifier" (GUID) in SQL Server (2016), and publishing them via
Geoserver (2.16.2).
We have had those limitations when displaying and editing them for a while in
earlier versions, but it looks
Phil,
If GeoServer is proxied, then the Global Setting 'Proxy Base URL' may
need to set.[1]
In my experience, that's one of the first settings I check when I hear
that things aren't quite working.:) For example, having that URL unset
with a proxy is the fastest way to trash proper OGC
Hi all,I am trying to cascade the following external WFShttps://fbinter.stadt-berlin.de/fb/wfs/data/senstadt/s_brw_2020?request=getcapabilities=wfs=1.1.0 Loading as new datastore and adding as new layer works. In the layer settings I can see all feature properties.The problem is, that one of
that ftl is on lib dir
gs-wms-2..jar
Phil Scadden escreveu no dia quarta, 11/03/2020 à(s)
22:55:
> Thanks Jim. What I suspect, is that someone has hacked the ftl on the
> geoserver instance because of the way that the geoserver instance is
> proxied. I was wondering where the flt was on the
