So as an end result of this will we have a single http(s) client through
out the library? So we can get proxy settings etc centralized for all GT/GS
stores?
If so sounds good to me
Ian
On Fri, 28 Feb 2020 at 14:40, Jody Garnett wrote:
> I really like this idea, and look forward to checking
I really like this idea, and look forward to checking out the proposal.
There are a lot of libraries and places to configure that would need to be
covered.
When you have a better idea on the geotools changes required can we make a
proposal there also. May also need to have this as a standing
Hi Mark,
Thank for the feedback
Allowing anything by default until a rule is added, sounds reasonable.
regards,
Imran
On Fri, Feb 28, 2020 at 4:48 PM Mark Prins wrote:
> On 28-02-2020 12:20, Imran Rajjad wrote:
> > Dear All,
> > I would like to submit the following GSIP :
> >
On 28-02-2020 12:20, Imran Rajjad wrote:
Dear All,
I would like to submit the following GSIP :
https://github.com/geoserver/geoserver/wiki/GSIP-189
*Some Background and Context:*
**
Geotools and Geoserver make a lot of HTTP calls, internally and
externally for different purposes which
Dear All,
I would like to submit the following GSIP :
https://github.com/geoserver/geoserver/wiki/GSIP-189
*Some Background and Context:*
Geotools and Geoserver make a lot of HTTP calls, internally and externally
for different purposes which include
- Downloading Schemas
- Requesting
Hi all
We occasionally make use of CQL in our GeoServer layer definition (in Add a
new layer, the very last option before Save is `Restrict the features on
layer by CQL filter`.
My first question to the GeoServer team is: is this restricted to CQL, or
does it allow ECQL too? I am assuming that
