Re: [Geoserver-users] GetFeature proxy redirection

2020-10-05 Thread Andrea Aime
On Mon, Oct 5, 2020 at 1:43 PM Nicolas De Ville de Goyet <
ndevi...@naturalsciences.be> wrote:

> So I'm a bit confuse at where I should fix the problem... I'm downloading
> directly on geoserver so it should understand the URL encoding?!
>

My guess is that the proxy is url-encoding again the already url-encoded
links from the preview. If I copy a link from it, instead of clicking on
it,
I already have all the URL-encoding there should be:

https://tb16.geo-solutions.it/geoserver/oszoom/ows?service=WFS=1.0.0=GetFeature=oszoom%3Aairports=50

A common proxy error is to doubly URL encode some parts of it, like turning
the typeName into oszoom%253Aairports
Just an hypothesis, mind

Cheers
Andrea

== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
(LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Re: [Geoserver-users] GetFeature proxy redirection

2020-10-05 Thread Nicolas De Ville de Goyet

Hello Andrea,

Thanks for your reply.

The error arise when I'm in the Layer preview page on geoserver itself. 
The url is this one: https://spatial.naturalsciences.be/geoserver/web/


To reproduce the error, search the layer borehole. Then download the gml 
preview (max 50 features):


http://spatial.naturalsciences.be/geoserver/ge/ows?service=WFS=1.0.0=GetFeature=*ge%3Aborehole*=50

--> error message: locator="typeName"> Feature type :ge%3Aborehole unknown 


Then correcting the url:

http://spatial.naturalsciences.be/geoserver/ge/ows?service=WFS=1.0.0=GetFeature=*ge:borehole*=50

I get the output I need.

So I'm a bit confuse at where I should fix the problem... I'm 
downloading directly on geoserver so it should understand the URL encoding?!


Any advice?

Thanks a lot,

Nicolas

On 05/10/2020 12:55, Andrea Aime wrote:
On Mon, Oct 5, 2020 at 12:31 PM Nicolas De Ville de Goyet 
mailto:ndevi...@naturalsciences.be>> wrote:


My problem is that the proxy translates the 'special' characters
in hexadecimal form in the GetFeature request (i.e.:
workspace:feature --> workspace%3Afeature) and geoserver is not
able to understand the request.

That looks like URL encoding, GeoServer is able to recognize it as 
long as the request is a GET request.
If the request is a POST XML and the contents of the XML have been URL 
encoded, then well, it won't of course.


An example of URL encoded that just works with an online GeoServer:
https://tb16.geo-solutions.it/geoserver/oszoom/ows?service=WFS=1.0.0=GetFeature=oszoom%3Aairports=50

By the way, the URL encoding is not really handled by GeoServer, it's 
the web container running GeoServer that handles it, e.g., Jetty, or 
Tomcat, or whatever is used in your installation.

GeoServer receives the request already decoded.

Cheers
Andrea

== GeoServer Professional Services from the experts! Visit 
http://goo.gl/it488V for more information. == Ing. Andrea Aime 
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 
55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: 
+39 339 8844549 http://www.geo-solutions.it 
http://twitter.com/geosolutions_it 
--- /Con 
riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si 
precisa che ogni circostanza inerente alla presente email (il suo 
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è 
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il 
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra 
operazione è illecita. Le sarei comunque grato se potesse darmene 
notizia. This email is intended only for the person or entity to which 
it is addressed and may contain information that is privileged, 
confidential or otherwise protected from disclosure. We remind that - 
as provided by European Regulation 2016/679 “GDPR” - copying, 
dissemination or use of this e-mail or the information herein by 
anyone other than the intended recipient is prohibited. If you have 
received this email by mistake, please notify us immediately by 
telephone or e-mail./



--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Re: [Geoserver-users] GetFeature proxy redirection

2020-10-05 Thread Andrea Aime
On Mon, Oct 5, 2020 at 12:31 PM Nicolas De Ville de Goyet <
ndevi...@naturalsciences.be> wrote:

> My problem is that the proxy translates the 'special' characters in
> hexadecimal form in the GetFeature request (i.e.: workspace:feature -->
> workspace%3Afeature) and geoserver is not able to understand the request.
>
That looks like URL encoding, GeoServer is able to recognize it as long as
the request is a GET request.
If the request is a POST XML and the contents of the XML have been URL
encoded, then well, it won't of course.

An example of URL encoded that just works with an online GeoServer:
https://tb16.geo-solutions.it/geoserver/oszoom/ows?service=WFS=1.0.0=GetFeature=oszoom%3Aairports=50

By the way, the URL encoding is not really handled by GeoServer, it's the
web container running GeoServer that handles it, e.g., Jetty, or Tomcat, or
whatever is used in your installation.
GeoServer receives the request already decoded.

Cheers
Andrea


== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
(LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


[Geoserver-users] GetFeature proxy redirection

2020-10-05 Thread Nicolas De Ville de Goyet

Hello everyone,

I'm struggling with GetFeature requests to geoserver behind a proxy.

I followed the instructions here and modified the web.xml document to 
allow the redirection:


/https://docs.geoserver.org/latest/en/user/security/webadmin/csrf.html/

My problem is that the proxy translates the 'special' characters in 
hexadecimal form in the GetFeature request (i.e.: workspace:feature --> 
workspace%3Afeature) and geoserver is not able to understand the request.


Any advice how to configure geoserver or the proxy to solve the issue?

Many thanks/
/

--
Nicolas de Ville
Belgian Marine Data Centre (BMDC)
OD-Nature, Royal Belgian Institute of Natural Sciences
02/627.42.79
www.bmdc.be
https://metadata.naturalsciences.be/

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users