I can uriencode the entire url. This link shows how it could be done with
javascript:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI
Or you can look up what the escaped . character would be and use that.
From: Gus MacAulay
Sent: Tuesday, 5 April 2022
Hi List,
I'm trying to use the REST API to enable/disable users, but running into an
issue when the username contains punctuation like @ or . (if the username is an
email for example).
If I create a user 't...@test.com' and do this:
curl -H 'Content-Type: application/json' -X POST
Thank you for the response Brad! Yes, I'm interested in setting up my own
geocaching server that a small private group could use to drop items at various
locations to be found by others, like in the Wikipedia link you provided.
I suppose there's no already made plug-in or web application
Hi Jukka,
it's just because that issue has been fixed only recently, a few months ago
(see my other mail on the topic).
The uncommon combination is not involving the INSPIRE plugin per se, but
I'm guessing, telling GeoServer
to use "strict OGC compliance", otherwise it would not throw an
Hi,
The GetCapabilities of the fresh Geoserver installation with the demo layers
http://localhost:8080/geoserver/ows?service=wms=1.3.0=GetCapabilities
do have all the GetLegendGraphics URLs with =. For example top:states
http://www.w3.org/1999/xlink; xlink:type="simple"
See this ticket, fixed beginning of 2022:
https://osgeo-org.atlassian.net/browse/GEOS-10336
Cheers
Andrea
On Mon, Apr 4, 2022 at 2:35 PM Elena Grigoriou
wrote:
> Indeed the version parameter is mandatory!
>
> So it seems that geoserver does not form the request according to the
> standard.
>
Indeed the version parameter is mandatory!
So it seems that geoserver does not form the request according to the
standard.
Let's see if there is a workaround or any configuration steps to overcome
this issue...
On Mon, 4 Apr 2022 at 11:35, Rahkonen Jukka (MML) <
Hi,
By what reference the version is optional? I had a look at the “Styled Layer
Descriptor profile of the Web Map Service Implementation Specification” and
there, in Table 9 —GetLegendGraphic operation request URL parameters the WMS
version is defined to be mandatory.
GetLegendGraphics works
Hi,
I am using Geoserver 2.20.2.
I have configured various wms. An example is the following:
http://beta.geoportal.ypen.gr/geoserver/aqd-wms/ows?service=wms=1.3.0=GetCapabilities
In the capabilities document, I find the GetLegendGraphic request, which
seems well formed based on the standard.
The
Hi,
the monitoring module collects various information about the requests and
responses,
including the request user and response size.
The only currently supported way to use monitoring is the "audit logging"
mode
10 matches
Mail list logo