Hi,
I understand that this suggestion is more involved in GeoServer codebase than
GeoTools.
And I also understand you want to keep a narrow scope.
But it brings on some interesting thoughts. What about MonitoringHTTPClient?
Hilsen Roar
> 23. mar. 2023 kl. 10:50 skrev Andrea Aime :
>
> HI
HI Roar,
for the first round of implementation, I have no place that's actually
using the GeoTools HTTPClient interface.
Given this would be a wrapper, it does not seem much of a HTTPBehavior, but
more of a hint, where the hint
value would be the URLChecker to use.
Generally speaking, I'd expect
Hi Jody,
the proposal indicates the scope of the initial implementation: WMS remote
SLD, WMS feature portrayal, WPS remote inputs.
That said, yes, entity resolution as set up in AllowListEntityResolver
could be rewritten to operate
against a URLChecker... I guess the GeoServer URL checker could
Hi,
Ok, got that.
Regards, Roar
> 23. mar. 2023 kl. 00:09 skrev Jody Garnett :
>
> Roar:
>
> I was mostly interested in clarifying the api; I just had an experience with
> enabling/disabling resources for different layers that had a similar OR test
> where any true was sufficient - and it
