Re: [Geoserver-users] Shapfile of type polygon showing point features in WMS

2019-04-25 Thread Naresh N
Naresh N 
Thu, Apr 25, 4:57 PM (16 hours ago)
to me
Dear Andrea,
I have found the code in the link
https://github.com/geotools/geotools/blob/13.4/modules/plugin/jdbc/jdbc-postgis/src/main/java/org/geotools/data/postgis/PostGISDialect.java
and
code is as follows

  String geomType = CLASS_TO_TYPE_MAP.get(gd.getType().getBinding());
if (geomType == null) {
geomType = "GEOMETRY";
}

If I want to do the changes and debug (like printing or alert messages) the
code , where do we can see the log/print messages in GeoServer?

Thanks,
Naresh



On Thu, Apr 25, 2019 at 3:34 PM Naresh N  wrote:

> Dear Andrea,
>
> Thanks a lot for your quick response.
>
> Thanks,
> Naresh
>
> On Thu, Apr 25, 2019 at 2:54 PM Andrea Aime 
> wrote:
>
>> On Thu, Apr 25, 2019 at 11:19 AM Naresh N  wrote:
>>
>>> * Is it possible to find the in GeoServer2.7.4, which part of the code
>>> deals with PostgreSQL table layer publishing? Kindly help me in
>>> this regard.*
>>>
>>
>> GeoServer 2.7.4 source code is here:
>> https://github.com/geoserver/geoserver/tree/2.7.4
>> It depends on a GeoTools 13.4, source code here:
>> https://github.com/geotools/geotools/tree/13.4
>>
>> The code you're looking for is quite likely in this module:
>>
>> https://github.com/geotools/geotools/tree/13.4/modules/plugin/jdbc/jdbc-postgis/src/main/java/org/geotools/data/postgis
>>
>> Good luck!
>>
>> 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] Shapfile of type polygon showing point features in WMS

2019-04-25 Thread Naresh N
Dear Andrea,

Thanks a lot for your quick response.

Thanks,
Naresh

On Thu, Apr 25, 2019 at 2:54 PM Andrea Aime 
wrote:

> On Thu, Apr 25, 2019 at 11:19 AM Naresh N  wrote:
>
>> * Is it possible to find the in GeoServer2.7.4, which part of the code
>> deals with PostgreSQL table layer publishing? Kindly help me in
>> this regard.*
>>
>
> GeoServer 2.7.4 source code is here:
> https://github.com/geoserver/geoserver/tree/2.7.4
> It depends on a GeoTools 13.4, source code here:
> https://github.com/geotools/geotools/tree/13.4
>
> The code you're looking for is quite likely in this module:
>
> https://github.com/geotools/geotools/tree/13.4/modules/plugin/jdbc/jdbc-postgis/src/main/java/org/geotools/data/postgis
>
> Good luck!
>
> 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] Shapfile of type polygon showing point features in WMS

2019-04-25 Thread Naresh N
Dear Andrea and Brad,

Thanks for responding and suggestions

As per my understanding when we are publishing postgresql table in
Geoserver 2.7.4, some have misinterpreted the-geom type and it is showing
as Geometry and assigned default point SLD.
GeoServer assigning for all the PostgreSQL/PostGIS
tables(point/polygon/line) published layers to default SLD.  I have tested
by deploying separate GeoServer 2.7.4 Instance and PostgreSQL 10.6/PostGIS
2.5.2 Instance and the result is same.
If we use PostgreSQL9.6/9.2 and if we publish the PostgreSQL table in
GeoServer 2.7.4 , it is assigning proper SLD based on PostgreSQL table
geometry type
Now I understand that, *GeoServer 2.7.4 not able to find the proper
'the_geom' type form PostgreSQL10.6 table geometry type and assigning
default point sld to every table*
* Is it possible to find the in GeoServer2.7.4, which part of the code
deals with PostgreSQL table layer publishing? Kindly help me in
this regard.*

*Thanks,*
*Naresh*




On Thu, Apr 25, 2019 at 11:44 AM Andrea Aime 
wrote:

> On Wed, Apr 24, 2019 at 2:21 PM Naresh N  wrote:
>
>> Dear Brad,
>> Thanks for quick response.
>> 1. I am deploying GeoNode 2.4 version which has customized version of
>> GeoServer which is 2.7.4. So I can not upgrade to higher version of
>> GeoServer.
>>
>
> As Brad said, upgrade if you can, you're running  on a really old version,
> hard to get any support for it (free or otherwise), I believe the current
> stable is 2.8.
>
>
>> 2. In database after uploading shape file 9f type polygon , i have
>> verified geom column type it showing as property with multi polygon.
>>
>
> The open shapefile specification (
> https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf) has no
> distinction between polygon and multipolygon,
> so the code defaults to multipolygon. ESRI might have added some extra
> sidecar file with a better description, but if there is any such file,
> GeoTools (the library reading the shapefile) cannot read it.
>
> As per my understanding when we are publishing postgresql table in
>> Geoserver 2.7.4, some have misinterpreted the-geom type and it is showing
>> as Geometry and assigned default point SLD.
>>
>
> This seems to be unlikely, the default style selector picks the "polygon"
> style for both simple and multi-polygons. But then again, I don't know how
> GeoNode interacts with GeoServer so maybe it's not using the GeoServer
> defaults and doing its own custom thing, you should ask on the GeoNode
> lists.
> Or maybe someone modified the style, by SLD rules a polygon is to be
> depicted as a point if the style uses a point symbolizer.
>
> 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] Shapfile of type polygon showing point features in WMS

2019-04-24 Thread Naresh N
Dear Brad,
Thanks for quick response.
1. I am deploying GeoNode 2.4 version which has customized version of
GeoServer which is 2.7.4. So I can not upgrade to higher version of
GeoServer.
2. In database after uploading shape file 9f type polygon , i have verified
geom column type it showing as property with multi polygon. As per my
understanding when we are publishing postgresql table in Geoserver 2.7.4,
some have misinterpreted the-geom type and it is showing as Geometry and
assigned default point SLD. Only problem is compatlblity of Geoserver 2.7.4
with postgresql 10.6 and. PostGIS 2.5.2

So if we know In Geoserver which part of code vetifies and asdigns the
the_grom type we can chbage/fix the code.

Kindly help me in this regards

Thanks,
NARESH

On Wed, Apr 24, 2019, 3:26 PM  wrote:

> GeoServer 2.7.4 is pretty old. Perhaps trying an upgrade first would be a
> good idea. After that, you could double-check how you created the database
> table - what does postgis think the data type is?
>
> In any case, you can probably just assign whichever default style you want
> using the UI. See
>
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#wms-sett
> ings
>
> Brad
>
> -Original Message-
> From: naresh 
> Sent: Wednesday, 24 April 2019 7:13 PM
> To: geoserver-users@lists.sourceforge.net
> Subject: [Geoserver-users] Shapfile of type polygon showing point features
> in WMS
>
> Hello All,
>
> I am using GeoServer2.7.4 ,PostgreSQL 10.7 and PostGIS 2.5.2. I have
> uploaded the shapefile of type polygon/line to PosgresQL Database(PostGIS
> enabled). Created the store from PostgreSQL/PostGIS in GeoServer.  I have
> published the PostgreSQL table( Uploaded Shapefile type of poygon) , then
> GeoServer assigns Default POINT SLD to it instead of assigning polygon.
> Please find the attached screenshot which shows *the_geom* type as
> *Geometry* which is wrong.
>
> Kindly help how to fix the issue. Which part of GeoServer code assigns
> *the_geom* type?
>
> Please let me know any other information required further
>
> Thanks,
> Naresh
>
>
>
>
>
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
>
>
> ___
> 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-inte
> grating-new-features-and-improvements-in-GeoServer
> 
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
___
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] Disabling error response of WMS/WFS to the Clients/users

2018-09-19 Thread Naresh N
Dear All,
Thanks a lot for responding and sharing the thoughts.

Best Regards,
Naresh.N

On Wed, Sep 19, 2018 at 2:12 PM Andrea Aime 
wrote:

> On Wed, Sep 19, 2018 at 10:21 AM Naresh N  wrote:
>
>> I request GeoServer developers community to include/enable generic error
>> messages in case of exception in future builds of GeoServer.
>>
>
> That is now how it works, the GPL license is clear:
>
> NO WARRANTY
>
>   11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
> FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
> OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
> PROVIDE* THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
> EXPRESSED*
> *OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF*
> *MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.*  *THE ENTIRE RISK
> AS*
> *TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU*.*  SHOULD THE*
> *PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,*
> *REPAIR OR CORRECTION.*
>
>   12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
> WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
> REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
> INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
> OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
> TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
> YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
> PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
> POSSIBILITY OF SUCH DAMAGES.
>
> If you want something done in GeoServer, either provide a pull request
> with the changes, following
> the contributiong guidelines [1], or contact a commercial support provider
> to have the changes developed for you [2]
>
> Cheers
> Andrea
>
> [1]: https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md
> [2]: http://geoserver.org/support/
>
> ==
>
> 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] Disabling error response of WMS/WFS to the Clients/users

2018-09-19 Thread Naresh N
Dear All,

Thanks a lot for sharing your views. The discussion I have started here
,because of our organisation security guidelines, the displayed error
messages were reported as security threat. Presently GeoServer displaying
exception as per OGC WMS standards for WMS Layer, but only instead of
displaying background programming details like Java,etc, it could have
better it displays the error message with out any background technology
used  at server side. And I feel it is  possible in jar files of Geoserver
which deals the exception. I request GeoServer developers community to
include/enable generic error messages in case of exception in future builds
of GeoServer.

Thanks a lot once again.

Best Regards,
Naresh

On Tue, Sep 18, 2018 at 11:43 PM Jonathan Moules <
jonathan-li...@lightpear.com> wrote:

> Hi Jukka,
>
> I think this is highlighting that there are different kinds of error
> messages, and I suspect (just guessing here) that the way GeoServer handles
> them is that it simply does not differentiate - they probably mostly get
> caught in the same way/place.
>
> Server side errors (which can be walls of technical text and stuffed away
> in the logs - they're for the techy server admin), and the admin-user
> errors. Currently GeoServer doesn't really differentiate which is why I
> took a gentle(!) poke at the user-friendliness component of the current
> admin-user errors, as such folks aren't necessarily techy. Unless something
> has changed since last I looked, the stack-traces you get for something
> like an SLD error are ... intimidating to a less-technical user. There are
> also the public-end-user errors (didn't include the "Request=" parameter
> for instance), but those are typically defined as OGC exceptions and
> usually get back a suitable (if XML-verbose) response.
>
> But it's all pie-in-the-sky thinking unless someone contributes a patch
> (or money for). So...
>
> Cheers,
>
> Jonathan
>
> On 18/09/2018 18:06, Rahkonen Jukka (MML) wrote:
>
> Hi,
>
>
>
> But users can’t check the server log and if they could it would probably
> be higher security risk. Error messages exist for helping the users to
> understand what they did wrong. Disabling error messages would leave them
> all alone. If it feels reasonable in your environment I guess it would not
> be very difficult to program a proxy the rips the error messages out or
> rewrites them to some neutral message.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* Jason Newmoyer [mailto:ja...@newmoyergeospatial.com
> ]
> *Lähetetty:* 18. syyskuuta 2018 18:29
> *Vastaanottaja:* jonathan-li...@lightpear.com
> *Kopio:* GeoServer Mailing List List
> 
> 
> *Aihe:* Re: [Geoserver-users] Disabling error response of WMS/WFS to the
> Clients/users
>
>
>
> I think a "suppress error messages" mode would be a nice-to-have feature.
> It would certainly make our customers happy to see those findings disappear
> from scan reports.
>
>
>
> Also, the full error messages should pretty much always be available in
> the server log. Displaying a generic error and saying "please check the
> server log" doesn't seem unreasonable.
>
>
>
> Jason
>
>
>
>
> Jason Newmoyer
> Newmoyer Geospatial Solutions
>
> 843.606.0424
>
> ja...@newmoyergeospatial.com
>
>
>
>
>
> On Mon, Sep 17, 2018 at 3:31 PM, Jonathan Moules <
> jonathan-li...@lightpear.com> wrote:
>
> Hi Naresh,
>
> I do not believe it is possible which is why Ian was suggesting
> improvements are always welcome.
>
> Needless to say, security through obscurity is pretty poor security, which
> is likely why this hasn't been done yet. Even as merely one layer of
> security. If your security relies on an attacker not knowing your database
> vendor and/or version, you have bigger problems than the content of an
> error message. If your db version is anything other than something very
> close to "latest-stable" then you are already likely open to have known
> vulnerabilities, and there are only a tiny handful of real database options.
>
> Now, from a user-friendliness perspective, a more user-friendly error than
> GeoServer's "here's a big wall of scary technical stuff that only really
> means anything to a few dozen people in the world" would be great, at least
> for the basic errors like "your SLD is borked". That said, posting parts of
> said big wall to this list does frequently elicit the help of such
> people... so... swings and roundabouts.
>
> Cheers,
>
> Jonathan
>
>
>
> On 12/09/2018 09:36, Naresh N wrote:
>
> Dear All,
>
> Is it possible to display generice error messages by doi

Re: [Geoserver-users] Disabling error response of WMS/WFS to the Clients/users

2018-09-12 Thread Naresh N
Dear All,
Is it possible to display generice error messages by doing any settings in
Geoserver.   If it is not possible , is there any way  not
displaying/showing any kind of error messages to users.

Please let me know.

Thanks,
Naresh

On Tue, Sep 11, 2018 at 6:34 PM Ian Turton  wrote:

> We're always happy to receive improvements.
>
> Ian
>
> On Tue, 11 Sep 2018 at 13:52, Calliess Daniel Ing. <
> daniel.calli...@stadt-salzburg.at> wrote:
>
>> Hello Jukka,
>>
>>
>>
>> the 'java.lang.NumberFormatException' is only one example for error
>> messages that expose system details. There might be a lot of other
>> information that will be shown to potential attackers when detailed error
>> messages are shown to the user, f.e. database related errors showing the
>> database vendor (and indirectly also the database version).
>>
>>
>>
>> So I also think that error messages should be more generic!
>>
>>
>>
>> Regards
>>
>> Daniel
>>
>>
>>
>>
>>
>> *From:* Naresh N [mailto:naresh...@gmail.com]
>> *Sent:* Friday, August 31, 2018 11:20 AM
>> *To:* jukka.rahko...@maanmittauslaitos.fi
>> *Cc:* Geoserver-users@lists.sourceforge.net
>> *Subject:* Re: [Geoserver-users] Disabling error response of WMS/WFS to
>> the Clients/users
>>
>>
>>
>>  Dear Jukka Rahkonent,,
>>
>>
>>
>> Thanks a lot for response and explaining detail.
>>
>>
>>
>> Best Regards,
>>
>> Naresh.N
>>
>>
>>
>> On Thu, Aug 30, 2018 at 5:56 PM Rahkonen Jukka (MML) <
>> jukka.rahko...@maanmittauslaitos.fi> wrote:
>>
>> Hi,
>>
>>
>>
>> If you use just non-supported outputformat
>>
>>
>> http://localhost:8080/geoserver/topp/wms?service=WMS=1.1.0=GetMap=topp%3Astates=-124.7314220001%2C24.955967%2C-66.969849%2C49.371735=768=330=EPSG%3A4326=image/png88
>>
>>
>>
>> then the error is
>>
>> 
>>
>>   There is no support for creating maps in image/png88 format
>>
>>
>>
>> Your error comes from non-numeric height parameter
>>
>>
>> http://localhost:8080/geoserver/topp/wms?service=WMS=1.1.0=GetMap=topp%3Astates=-124.7314220001%2C24.955967%2C-66.969849%2C49.371735=768=acu330=EPSG%3A4326=image/png8
>>
>> gives similar error
>> 
>>
>>   java.lang.NumberFormatException: For input string:
>> acu330
>>
>>
>>
>> By reading the WMS 1.3.0 standard such invalid WIDTH and HEIGHT
>> parameters are not really deald in it. What is closest is in this:
>> “If the WMS server has declared that a Layer has fixed width and height,
>> as described in 7.2.4.7.5, then the client shall specify exactly those
>> WIDTH and HEIGHT values in the GetMap request and the server may issue a
>> service exception otherwise.”
>>
>>
>>
>> The message reveals that server is Java based which is something that the
>> end user does not need to know. It is also telling that number format used
>> in the request is not correct and that’s useful information for the user.
>> Disabling the whole exception in not possible because it is mandatory. So
>> what is left is filtering the “java.lang” away. I believe it could be done
>> (I am not a developer) but I believe that it would not be any huge
>> improvement for the security. If somebody proves that I am wrong I can
>> change my mind.
>>
>>
>>
>> -Jukka Rahkonen-
>>
>>
>>
>>
>>
>>
>>
>> *Lähettäjä:* Naresh N [mailto:naresh...@gmail.com]
>> *Lähetetty:* 30. elokuuta 2018 9:52
>> *Vastaanottaja:* Rahkonen Jukka (MML) > ahko...@maanmittauslaitos.fi>
>> *Aihe:* Re: [Geoserver-users] Disabling error response of WMS/WFS to the
>> Clients/users
>>
>>
>>
>> Dear  Dear Jukka Rahkonent,
>>
>>
>>
>> Please find the below request
>>
>>
>> http://bhuvan-suvidha.nrsc.gov.in/geoserver/wms/reflect?layers=geonode:kds_name=200=150=image/png8
>>
>>
>> rmat=image/png8=acu7746%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9uca7746=geonode
>>
>> :kds_name=200
>>
>>
>>
>> The above request is generated by Web Application Security tool, and is
>> is listed as security alert as it is showing the error message as
>> java.lang.Number Format Exception.  Recommendation is to disable the error
>> message. Kindly help me to resolve this.
>>
>>
>>
>> Thanks,
>>
>> Naresh
>>
>>
>>
&g

Re: [Geoserver-users] Disabling error response of WMS/WFS to the Clients/users

2018-08-31 Thread Naresh N
 Dear Jukka Rahkonent,,

Thanks a lot for response and explaining detail.

Best Regards,
Naresh.N

On Thu, Aug 30, 2018 at 5:56 PM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> If you use just non-supported outputformat
>
>
> http://localhost:8080/geoserver/topp/wms?service=WMS=1.1.0=GetMap=topp%3Astates=-124.7314220001%2C24.955967%2C-66.969849%2C49.371735=768=330=EPSG%3A4326=image/png88
>
>
>
> then the error is
>
> 
>
>   There is no support for creating maps in image/png88 format
>
>
>
> Your error comes from non-numeric height parameter
>
>
> http://localhost:8080/geoserver/topp/wms?service=WMS=1.1.0=GetMap=topp%3Astates=-124.7314220001%2C24.955967%2C-66.969849%2C49.371735=768=acu330=EPSG%3A4326=image/png8
>
> gives similar error
> 
>
>   java.lang.NumberFormatException: For input string: acu330
>
>
>
> By reading the WMS 1.3.0 standard such invalid WIDTH and HEIGHT parameters
> are not really deald in it. What is closest is in this:
> “If the WMS server has declared that a Layer has fixed width and height,
> as described in 7.2.4.7.5, then the client shall specify exactly those
> WIDTH and HEIGHT values in the GetMap request and the server may issue a
> service exception otherwise.”
>
>
>
> The message reveals that server is Java based which is something that the
> end user does not need to know. It is also telling that number format used
> in the request is not correct and that’s useful information for the user.
> Disabling the whole exception in not possible because it is mandatory. So
> what is left is filtering the “java.lang” away. I believe it could be done
> (I am not a developer) but I believe that it would not be any huge
> improvement for the security. If somebody proves that I am wrong I can
> change my mind.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* Naresh N [mailto:naresh...@gmail.com]
> *Lähetetty:* 30. elokuuta 2018 9:52
> *Vastaanottaja:* Rahkonen Jukka (MML)  >
> *Aihe:* Re: [Geoserver-users] Disabling error response of WMS/WFS to the
> Clients/users
>
>
>
> Dear  Dear Jukka Rahkonent,
>
>
>
> Please find the below request
>
>
> http://bhuvan-suvidha.nrsc.gov.in/geoserver/wms/reflect?layers=geonode:kds_name=200=150=image/png8
>
>
> rmat=image/png8=acu7746%EF%BC%9Cs1%EF%B9%A5s2%CA%BAs3%CA%B9uca7746=geonode
>
> :kds_name=200
>
>
>
> The above request is generated by Web Application Security tool, and is is
> listed as security alert as it is showing the error message as
> java.lang.Number Format Exception.  Recommendation is to disable the error
> message. Kindly help me to resolve this.
>
>
>
> Thanks,
>
> Naresh
>
>
>
> On Thu, Aug 30, 2018 at 11:17 AM Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
> Hi,
>
> Please show the whole request with the wrong = parameter.
>
> -Jukka Rahkonen-
> --
>
> *Lähettäjä: *Naresh N 
> *Lähetetty: *‎30.‎8.‎2018 7:22
> *Vastaanottaja: *Rahkonen Jukka (MML)
> 
> *Aihe: *Re: [Geoserver-users] Disabling error response of WMS/WFS to the
> Clients/users
>
> Dear Jukka Rahkonent,
>
>
>
> Thanks for the response. The error message  ' java.lang.Number
> FormatException' belongs to InvaildFormat.  Instead of showing service
> exception i.,e java.lang.Number Format Exception, how to display
> InvalidFormat message to user. Although this erros is not displaying any
> sensitive information, as per our security alerts measure,  we want disable
> the error messages. Kindly let me know how to do.
>
>
>
> Thanks,
>
> Naresh
>
>
>
> On Wed, Aug 29, 2018 at 8:08 PM Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
> Hi,
>
> I suppose that you mean the contents " java.lang.NumberFormatException:
> For input string:".  Exceptions are compulsory by the WMS standard. The
> following codes are reserved for special meanings.
>
> InvalidFormat
> InvalidCRS
> LayerNotDefined
> StyleNotDefined
> LayerNotQueryable
> InvalidPoint
> CurrentUpdateSequence
> InvalidUpdateSequence
> MissingDimensionValue
> InvalidDimensionValue
> OperationNotSupported
>
> The error that triggers your error does not quite suit with these
> predefined meanings and therefore the error code must be something else.
> The code that you get now is "java.lang.NumberFormatException". At least it
> is somewhat informative but would you rather see some other text as an
> error message?
>
> Client can also ask exceptions in another format with =INIMAGE
> of 

[Geoserver-users] Accept me for posting the quries

2018-08-29 Thread Naresh N
Dear Sir/Madam,

Kindly allow me to post quires related to Geoserver

Thanks,
Naresh
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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