Re: [Geoserver-users] Filter out Layers from WMTS GetCapabilities Document based on Authorization in Data Security

[Steve Omondi]

On top of getCapabilities document size;

In terms of Security, users are only supposed to see the Metadata for the
Data (Layers) they are authorized to see, but even with the HIDE MODE on,
still all users can access Metadata for all layers in our Catalog in the
getCapabilites documents (both WMTS and WMS)?

Is this a normal Geoserver behaviour? In ideal situation this should not be
the case.

Running Geoserver 2.11.2 on Tomcat 8.

Kind regards,
Steve Omondi

On Thu, Feb 1, 2018 at 10:02 AM, Steve Omondi 
wrote:

> Hi guys,
>
> I'd like to filter out layers from the WMTS GetCapabilities Documemnt
> based on the Rules in Data Security so that I can reduce the size of the
> GetCapabilites Document (currently we download 3.8 MB everytime the Client
> map application loads - not good).
>
> The options I have tried are;
> 1. Using the Catalog Mode in data Security: HIDE does not work, still all
> users can download the full GetCapabilities Document as well as MIXED mode.
>
> 2. Turning OFF the Advertised flag in Layer Resource Info...this is not an
> option for us though.
>
> How can I achieve this? I mean filtering (hiding) layers from the
> GetCapabilties document depending on the Authorization a user has.
>
> Or
>
> How else can I ensure the GetCapabilites document downloaded whenever it's
> fetched is minimal.
>
> Any help appreciated.
>
> Kind regards,
> Steve Omondi
>
--
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

[Geoserver-users] Filter out Layers from WMTS GetCapabilities Document based on Authorization in Data Security

[Steve Omondi]

Hi guys,

I'd like to filter out layers from the WMTS GetCapabilities Documemnt based
on the Rules in Data Security so that I can reduce the size of the
GetCapabilites Document (currently we download 3.8 MB everytime the Client
map application loads - not good).

The options I have tried are;
1. Using the Catalog Mode in data Security: HIDE does not work, still all
users can download the full GetCapabilities Document as well as MIXED mode.

2. Turning OFF the Advertised flag in Layer Resource Info...this is not an
option for us though.

How can I achieve this? I mean filtering (hiding) layers from the
GetCapabilties document depending on the Authorization a user has.

Or

How else can I ensure the GetCapabilites document downloaded whenever it's
fetched is minimal.

Any help appreciated.

Kind regards,
Steve Omondi
--
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

Re: [Geoserver-users] Geoserver REST Reload with POST Request Returns ERROR 401 Full authentication is required to access this resource despite using admin user

[Steve Omondi]

​Hi,
​

> Are you using any specific configuration for the security system ?
>

​So, I'm runnning a number of non-default  configurations for my Geoserver;

The major configuration which has beena big problem is use of a different
Role Service (JDBC) as the Active Role Service -

This is a problem to GWC administration tasks like Seeding, truncate,
Configuration Reload since these require the Admin user found in default
role service.

Basically, It seems to me Geoserver and Integrated GWC can only work with
one Role Service at a time.
[image: Inline image 1]

Question...So I had Imagined creating the admin user in my JDBC Role
Service and delete the default Roles Service entirely but this is not
possible. Are these hardcoded somhow in Geoserver? Perhaps.

Kind regards,
Steve Omondi

On Thu, Jan 25, 2018 at 9:30 PM, Nuno Oliveira <
nuno.olive...@geo-solutions.it> wrote:

> Hi,
>
> Just did a quick test with a GeoServer 2.11.2 running inside a tomcat
> instance and everything worked as expected:
>
> curl -u 'admin:geoserver' -v --data-urlencode -POST 
> http://localhost:8080/geoserver/rest/reload
>
> *   Trying 127.0.0.1...
>
> * Connected to localhost (127.0.0.1) port 8080 (#0)
>
> * Server auth using Basic with user 'admin'
>
> > POST /geoserver/rest/reload HTTP/1.1
>
> > Host: localhost:8080
>
> > Authorization: Basic YWRtaW46Z2Vvc2VydmVy
>
> > User-Agent: curl/7.47.0
>
> > Accept: */*
>
> > Content-Length: 5
>
> > Content-Type: application/x-www-form-urlencoded
>
> >
>
> * upload completely sent off: 5 out of 5 bytes
>
> < HTTP/1.1 200 OK
>
> < Date: Thu, 25 Jan 2018 18:24:29 GMT
>
> < Server: Noelios-Restlet-Engine/1.0..8
>
> < Transfer-Encoding: chunked
>
> <
>
> * Connection #0 to host localhost left intact
>
> The error you are getting suggests indeed that you are using a login that
> doesn't have enough permissions to use
> that REST endpoint. I would double check that user configuration and give
> it a try with an administrator login.
>
> Are you using any specific configuration for the security system ?
>
> Kind regards,
>
> Nuno Oliveira
>
>
> On 01/25/2018 08:23 AM, Steve Omondi wrote:
>
> Hey guys,
> I'm trying to reload Geoserver configuration via a POST Request using CURL
> Utility but it fails with the following error;
>
> administrator@host:/media/config$ curl -u "admin:password" -v
> --data-urlencode -POST http://host:8380/geoserver/rest/reload
> *   Trying 127.0.1.1...
> * Connected to ros-gs3 (127.0.1.1) port 8380 (#0)
> * Server auth using Basic with user 'admin'
> > POST /geoserver/rest/reload HTTP/1.1
> > Host: host:8380
> > Authorization: Basic YWRtaW46UjRtYW5pdGFpbCAtbjIwMC
> AtZiAvbW50L3Jvcy1jb25maWcvcm9zLWxvZ3MvZ3MzMy9HUzMzYWRtaW4ubG9nIA==
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Content-Length: 5
> > Content-Type: application/x-www-form-urlencoded
> >
> * upload completely sent off: 5 out of 5 bytes
> < HTTP/1.1 401
> < Set-Cookie: remember-me=; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10
> GMT; Path=/geoserver
> * Authentication problem. Ignoring this.
> < WWW-Authenticate: Basic realm="GeoServer Realm"
> < Content-Type: text/html;charset=utf-8
> < Content-Language: en
> < Content-Length: 1171
> < Date: Thu, 25 Jan 2018 08:16:20 GMT
> <
> *HTTP Status 401 –
> Unauthorized*h1 {font-family:Tahoma,Arial,
> sans-serif;color:white;background-color:#525D76;font-size:22px;} h2
> {font-family:Tahoma,Arial,sans-serif;color:white;
> background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,
> sans-serif;color:white;background-color:#525D76;font-size:14px;} body
> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
> b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
> p 
> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
> a {color:black;} a.name {color:black;} .line
> {height:1px;background-color:#525D76;border:none;}HTTP
> Status 401 – UnauthorizedType Status
> ReportMessage No AuthenticationProvider found for
> org.springframework.security.authentication.UsernamePasswordAuthenticationTokenDescription
> The request has not been a* Connection #0 to host  left intact
> pplied because it lacks valid authentication credentials for the target
> resource.Apache Tomcat/8.5.13 html>
>
>
> The provided user and password are correct.
>
> I'm not able to access http://host:8381/geoserver/rest/reload on the web
> as well while I can access http://host:8381/geoserver/rest/all
> the/other/endpoints
>
> I have tried to do the same with Apache Jmeter, and this
> (/geoserver/rest/reload) is not available.
>
> Happens for Geoserver *2.11.2 running on Tomcat 8 as well as Geoserver
> 2.9 running o Jetty.*
>
> *I'm sure this is not normal, so anyone help me figure out what I'm
> missing please.*
>
> Kind regards,
> Steve Omondi
>
>
> 
>  Virus-free.
> www.avast.com
> 

Re: [Geoserver-users] Problem with creating LayerGroup using REST api

[Kris Powell]

Hi Anton,


I really appreciate the response. I now have layerGroups copying to the new 
workspaces nicely.


I retrieve all coverageStores, coverages, dataStores, featureTypes, and 
layerGroups from a workspace, modify the name and hrefs where necessary, then 
post back to the newly created workspace's endpoints.

Everything works well, except the styles - for some reason the styles aren't 
copied over to the cloned layers. Have you had any success with layer styles?


Thanks and regards,

Kris


From: Anton Bakker 
Sent: Thursday, 1 February 2018 3:03:49 AM
To: Kris Powell
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Problem with creating LayerGroup using REST api

Hi Kris,

For me the following request body works to create a new layergroup (on 
GeoServer 2.12, but should work for other versions as well):


  group_c
  CONTAINER
  group_c
  
  
charts
  
  

  charts:world_cities
  http://www.w3.org/2005/Atom” rel=“alternate" 
href="http:///geoserver/rest/layers/charts:world_cities.xml" 
type="application/xml" />


  charts:usa_states
  http://www.w3.org/2005/Atom; rel="alternate" 
href="http:///geoserver/rest/layers/charts:usa_states.xml" 
type="application/xml" />

  
  


  
  
-124.731422
151.206955
-37.817532
59.916269143887
EPSG:4326
  


So the published/name element should use the following format 
:, the same is true for the url of that layer.  Hope this 
helps!

Kind regards,
Anton Bakker
GeoCat BV


On 25 Jan 2018, at 02:34, Kris Powell 
> wrote:

Hi Tam,


Did you ever find out more about this issue?

I've been building a tool to clone existing workspaces including stores,
layers and layergroups, and I'm running into the same problem you mention
here. The response I receive from geoserver is:

`Layer group within a workspace (testworkspace) can not contain resources
from other workspace: existingworkspace`

when I POST a new layerGroup to
`.../rest/workspaces/testworkspace/layergroups`


Any light you or other subscribers could shed on this would be very helpful.

Regards,
Kris



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
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

--
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

[Geoserver-users] WPS Asynchronous Exception MissingParameterValue

[Reed, Raeschel]

Attempting to change wps request to be asynchronous. Original request, 
non-asynchronous, successfully returns json object. Modified request per 
instructions: 
http://docs.geoserver.org/stable/en/user/community/wps-download/index.html  
results in the expected status response. However attempting to hit the returned 
statusLocation url results in exception. What does this mean? What is missing 
from the request?


http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://www.opengis.net/wps/1.0.0;
   xmlns:wfs="http://www.opengis.net/wfs; 
xmlns:wps="http://www.opengis.net/wps/1.0.0;
   xmlns:ows="http://www.opengis.net/ows/1.1; 
xmlns:gml="http://www.opengis.net/gml;
   xmlns:ogc="http://www.opengis.net/ogc; 
xmlns:wcs="http://www.opengis.net/wcs/1.1.1;
   xmlns:xlink="http://www.w3.org/1999/xlink;
   xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 
http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd;>
   gs:OAMLMergedVerticalCrossSection
   
  ...
   
   
  
 
   result
 
  
   



http://www.w3.org/2001/XMLSchema;
   xmlns:ows="http://www.opengis.net/ows/1.1; 
xmlns:wps="http://www.opengis.net/wps/1.0.0;
   xmlns:xlink="http://www.w3.org/1999/xlink; xml:lang="en" service="WPS"
   serviceInstance="https://local:8443/geoserver/ows?;
   
statusLocation="https://local:8443/geoserver/ows?service=WPSversion=1.0.0request=GetExecutionStatusexecutionId=6199125e-6567-4bdf-b950-2b2e0de0a4ec;
   version="1.0.0">
   
  gs:OAMLMergedVerticalCrossSection
  OAMLMergedVerticalCrossSection
  Generates a merged vertical cross section of an 
OAML coverage
   
   
  Process accepted.
   


http://www.w3.org/2001/XMLSchema; 
xmlns:ows="http://www.opengis.net/ows/1.1; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; version="1.1.0" 
xsi:schemaLocation="http://www.opengis.net/ows/1.1 
https://local:8443/geoserver/schemas/ows/1.1.0/owsAll.xsd;>


Could not determine geoserver request from http request 
org.geoserver.platform.AdvancedDispatchFilter$AdvancedDispatchHttpRequest@28e99a8c





Raeschel Reed
Sr Software Engineer
General Dynamics Information Technology

--
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

[Geoserver-users] Delete nested layer group through REST API

[Anton Bakker]

Hi all,

I have a problem with removing layer groups and layers that are nested in layer 
groups through the REST API. 

Consider the following layers to be published in GeoServer:

- group_a
- group_b
- layer_1

When I delete layer group group_a through the REST API, the layer group group_b 
is also removed. After this I try to remove layer_1, I receive a HTTP 500 
internal server error response with the following message:

:Unable to delete layer referenced by layer group 'group_c'

Then I came up with a cunning plan to first remove the reference to layer_1 in 
group_c, but it turns out you cannot modify a layergroup to have no layers 
inside. The PUT request to create an empty layer group group_b returns a HTTP 
500 internal server error with the following message:

:Layer group must not be empty

Deleting layer group group_b before deleting group_a is not a option either, 
because group_b is referenced in layer group group_a. 

I found that this problem only occurs for GeoServer version 2.11 and 2.12.   
When you remove a layer group in GeoServer 2.10 (or lower presumably) it does 
not cascade down automatically. So in our example, when removing group_a it 
does not automatically remove group_b. And after removing group_b there is no 
error message when removing layer_1.

Seems like a bug to me, seems to be related to this bug 
https://osgeo-org.atlassian.net/browse/GEOS-8547. 

Any thoughts or suggestions are appreciated.

Kind regards,
Anton Bakker
GeoCat BV--
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

Re: [Geoserver-users] Problem with creating LayerGroup using REST api

[Anton Bakker]

Hi Kris,

For me the following request body works to create a new layergroup (on 
GeoServer 2.12, but should work for other versions as well):


  group_c
  CONTAINER
  group_c
  
  
charts
  
  

  charts:world_cities
  http://www.w3.org/2005/Atom” rel=“alternate" 
href="http:///geoserver/rest/layers/charts:world_cities.xml" 
type="application/xml" />


  charts:usa_states
  http://www.w3.org/2005/Atom; rel="alternate" 
href="http:///geoserver/rest/layers/charts:usa_states.xml" 
type="application/xml" />

  
  


  
  
-124.731422
151.206955
-37.817532
59.916269143887
EPSG:4326
  


So the published/name element should use the following format 
:, the same is true for the url of that layer.  Hope this 
helps!

Kind regards,
Anton Bakker
GeoCat BV


> On 25 Jan 2018, at 02:34, Kris Powell  wrote:
> 
> Hi Tam,
> 
> 
> Did you ever find out more about this issue?
> 
> I've been building a tool to clone existing workspaces including stores,
> layers and layergroups, and I'm running into the same problem you mention
> here. The response I receive from geoserver is:
> 
> `Layer group within a workspace (testworkspace) can not contain resources
> from other workspace: existingworkspace`
> 
> when I POST a new layerGroup to
> `.../rest/workspaces/testworkspace/layergroups`
> 
> 
> Any light you or other subscribers could shed on this would be very helpful.
> 
> Regards,
> Kris
> 
> 
> 
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
> 
> --
> 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

--
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

Re: [Geoserver-users] Table structure when hosting Image mosaic index in Oracle

[Paul Wittle via Geoserver-users]

Hi,

I'm not sure exactly what the issue was yesterday but it seems to have simply 
started working today.

I eventually tracked down that it had started to issue a SDO_TUNE.EXTENT_OF 
command and was also failing due to an issue with the spatial index 
(specifically the metadata entry). I resolved all those issues yesterday and 
was just left with the "WARN [imagemosaic.catalog] - This granule catalog was 
not properly dispose as it still points to:ServiceInfo  description=Features 
from JDBCDataStore" Message.

I was doing something else this morning but realised it had simply started 
working.

Hopefully this set of emails might save someone else some time though.

Cheers,
Paul

Message: 1
Date: Tue, 30 Jan 2018 10:33:24 +0100
From: Andrea Aime 
To: Paul Wittle 
Cc: "geoserver-users@lists.sourceforge.net"

Subject: Re: [Geoserver-users] Table structure when hosting Image
mosaic index in Oracle
Message-ID:

Content-Type: text/plain; charset="utf-8"

Hi Paul,
I believe there is a misunderstanding at play there. The text says "the 
database", not "the table".

With PostgreSQL we have ways to connect to the master template database and 
issue a "create database" there, so GeoServer with the right credentials can 
literally create a brand new database to host the index table (and after that, 
create the index table in it).

With Oracle that is not supported (not sure if it cannot be done, or we simply 
don't have the code to do that)... but it just means you have to point 
GeoServer to an existing database, and if the user has the right credentials, 
the "create table" will be done for you

Hope this helps

Cheers
Andrea


On Tue, Jan 30, 2018 at 8:54 AM, Paul Wittle via Geoserver-users < 
geoserver-users@lists.sourceforge.net> wrote:

> Hi,
>
>
>
> On the following page
> http://geoserver.geo-solutions.it/edu/en/multidim/
> imagemosaic/mosaic_datastore.html it states that I can use Oracle
> instead of a shapefile for my Image Mosaic index files.
>
>
>
> There is a statement that reads:
>
>
>
> When using an Oracle database to host the index it is necessary to
> create the database before serving the mosaic because it is not
> automatically created by the underlying code. This is because database
> creation is not supported in a standard way through JDBC drivers, and
> we have a custom solution working for PostGIS only at the time being.
>
>
>
> I?m assuming I need to create a table in the database for it to
> populate but is the required structure for the table published
> anywhere as I can?t find it?
>
>
>
> Thanks in advance ?
>
> Paul W
>
>
> "This e-mail is intended for the named addressee(s) only and may
> contain information about individuals or other sensitive information
> and should be handled accordingly. Unless you are the named addressee
> (or authorised to receive it for the addressee) you may not copy or
> use it, or disclose it to anyone else. If you have received this email
> in error, kindly disregard the content of the message and notify the
> sender immediately. Please be aware that all email may be subject to
> recording and/or monitoring in accordance with relevant legislation."
>
> 
> --
> 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
>
>


--

Regards,

Andrea Aime

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
? consentito esclusivamente al destinatario del messaggio, per le finalit? 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il