wms_enable_request header vs. layer

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

wms_enable_request header vs. layer

Jörg Thomsen (WhereGroup)
Hi,

I need an explanation for ows_enable_request.

There are two mapfiles, brw_enable_header.map and brw_enable_layer.map
The only difference is, that in
brw_enable_header.map I have enabled all ows requests within the
metadata-section in the header and in each layer.

In brw_enable_layer.map I only have enabled all requests in the
layer-section, but not in the header.

Both WMS allow the capability-request and in brw_enable_layer.map the
information for the wms-request is missing:
https://www.diffchecker.com/KjsX2Wbk

OK. The brw_enable_layer.map (with no ows_enable_reqeust in the header)
allows GetMap-Requests:
http://h2743629.stratoserver.net/cgi-bin/mapserv?map=/data/ows/map/brw_enable_layer.map&&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=48.60086340827337636,9.02229999999999954,48.65160000000000196,9.0733134442446044&CRS=EPSG:4326&WIDTH=426&HEIGHT=422&LAYERS=bodenrichtwertzone&STYLES=&FORMAT=image/png&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96&TRANSPARENT=TRUE

I think this is technically correct, but as the capabilities don't
provide any information for the getMap-Request (no online-ressource, no
image-formats), a client does not know this parameters. In the result I
cannot load the WMS into a mabpender-application.
I wonder why (and I am surprised) QGIS doesn't have any problems with
this wms.

Is this how it shall be? Is MapServer working correct or Mapbender? Or
both, but ...?

Regards, Jörg

--

***********************************
Where2B Konferenz 2017
14. Dezember 2017 in Bonn
www.where2b-conference.com
***********************************

_______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users
Reply | Threaded
Open this post in threaded view
|

Re: wms_enable_request header vs. layer

nmtoken
Technically QGIS (or any other client) is going against the WMS standard by requesting something not in GetCapabilities response, and MapServer is at fault for responding with something not advertised.

Of course a GetMap operation is mandatory for a WMS, so you might argue that MapServer is at fault for providing a GetCapabilities response that doesn't advertise a GetMap operation.

James

-----Original Message-----
From: mapserver-users [mailto:[hidden email]] On Behalf Of [hidden email]
Sent: 06 December 2017 20:00
To: [hidden email]
Subject: mapserver-users Digest, Vol 119, Issue 5

Send mapserver-users mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/mapserver-users
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..."


Today's Topics:

   1. wms_enable_request header vs. layer (Jörg Thomsen (WhereGroup))


----------------------------------------------------------------------

Message: 1
Date: Wed, 6 Dec 2017 13:41:36 +0100
From: Jörg Thomsen (WhereGroup)  <[hidden email]>
To: "[hidden email]"
<[hidden email]>
Subject: [mapserver-users] wms_enable_request header vs. layer
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8

Hi,

I need an explanation for ows_enable_request.

There are two mapfiles, brw_enable_header.map and brw_enable_layer.map The only difference is, that in brw_enable_header.map I have enabled all ows requests within the metadata-section in the header and in each layer.

In brw_enable_layer.map I only have enabled all requests in the layer-section, but not in the header.

Both WMS allow the capability-request and in brw_enable_layer.map the information for the wms-request is missing:
https://www.diffchecker.com/KjsX2Wbk

OK. The brw_enable_layer.map (with no ows_enable_reqeust in the header) allows GetMap-Requests:
http://h2743629.stratoserver.net/cgi-bin/mapserv?map=/data/ows/map/brw_enable_layer.map&&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=48.60086340827337636,9.02229999999999954,48.65160000000000196,9.0733134442446044&CRS=EPSG:4326&WIDTH=426&HEIGHT=422&LAYERS=bodenrichtwertzone&STYLES=&FORMAT=image/png&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96&TRANSPARENT=TRUE

I think this is technically correct, but as the capabilities don't provide any information for the getMap-Request (no online-ressource, no image-formats), a client does not know this parameters. In the result I cannot load the WMS into a mabpender-application.
I wonder why (and I am surprised) QGIS doesn't have any problems with this wms.

Is this how it shall be? Is MapServer working correct or Mapbender? Or both, but ...?

Regards, Jörg

--

***********************************
Where2B Konferenz 2017
14. Dezember 2017 in Bonn
www.where2b-conference.com
***********************************



------------------------------

Subject: Digest Footer

_______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users

------------------------------

End of mapserver-users Digest, Vol 119, Issue 5
***********************************************
________________________________
 This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
________________________________
_______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users
Reply | Threaded
Open this post in threaded view
|

Re: wms_enable_request header vs. layer

Jörg Thomsen (WhereGroup)
Moin,

I think the problem is, that the Layers allow the GetMap-Request and
MapServer does not provide the required Information in the capabilities.

Am I wrong?

Jörg



Am 07.12.2017 um 11:30 schrieb Passmore, James H.:> Technically QGIS (or
any other client) is going against the WMS standard by requesting
something not in GetCapabilities response, and MapServer is at fault for
responding with something not advertised.

>
> Of course a GetMap operation is mandatory for a WMS, so you might argue that MapServer is at fault for providing a GetCapabilities response that doesn't advertise a GetMap operation.
>
> James
>
> -----Original Message-----
> From: mapserver-users [mailto:[hidden email]] On Behalf Of [hidden email]
> Sent: 06 December 2017 20:00
> To: [hidden email]
> Subject: mapserver-users Digest, Vol 119, Issue 5
>
> Send mapserver-users mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..."
>
>
> Today's Topics:
>
>    1. wms_enable_request header vs. layer (Jörg Thomsen (WhereGroup))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 6 Dec 2017 13:41:36 +0100
> From: Jörg Thomsen (WhereGroup)  <[hidden email]>
> To: "[hidden email]"
> <[hidden email]>
> Subject: [mapserver-users] wms_enable_request header vs. layer
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> I need an explanation for ows_enable_request.
>
> There are two mapfiles, brw_enable_header.map and brw_enable_layer.map The only difference is, that in brw_enable_header.map I have enabled all ows requests within the metadata-section in the header and in each layer.
>
> In brw_enable_layer.map I only have enabled all requests in the layer-section, but not in the header.
>
> Both WMS allow the capability-request and in brw_enable_layer.map the information for the wms-request is missing:
> https://www.diffchecker.com/KjsX2Wbk
>
> OK. The brw_enable_layer.map (with no ows_enable_reqeust in the header) allows GetMap-Requests:
> http://h2743629.stratoserver.net/cgi-bin/mapserv?map=/data/ows/map/brw_enable_layer.map&&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=48.60086340827337636,9.02229999999999954,48.65160000000000196,9.0733134442446044&CRS=EPSG:4326&WIDTH=426&HEIGHT=422&LAYERS=bodenrichtwertzone&STYLES=&FORMAT=image/png&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96&TRANSPARENT=TRUE
>
> I think this is technically correct, but as the capabilities don't provide any information for the getMap-Request (no online-ressource, no image-formats), a client does not know this parameters. In the result I cannot load the WMS into a mabpender-application.
> I wonder why (and I am surprised) QGIS doesn't have any problems with this wms.
>
> Is this how it shall be? Is MapServer working correct or Mapbender? Or both, but ...?
>
> Regards, Jörg
>
> --
>
> ***********************************
> Where2B Konferenz 2017
> 14. Dezember 2017 in Bonn
> www.where2b-conference.com
> ***********************************
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> mapserver-users mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
> ------------------------------
>
> End of mapserver-users Digest, Vol 119, Issue 5
> ***********************************************
> ________________________________
>  This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
> ________________________________
> _______________________________________________
> mapserver-users mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>


Viele Grüße,
Jörg Thomsen

--

***********************************
Where2B Konferenz 2017
14. Dezember 2017 in Bonn
www.where2b-conference.com
***********************************

Jörg Thomsen
WhereGroup GmbH & Co. KG
Gillweg 3
14193 Berlin
Germany

Fon: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 89 09 53 21

[hidden email]
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
-------------------------------
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
-------------------------------
Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com
_______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users
Reply | Threaded
Open this post in threaded view
|

Re: wms_enable_request header vs. layer

jratike80
In reply to this post by Jörg Thomsen (WhereGroup)
Hi,

The development of this feature was done by http://mapserver.gis.umn.edu/pl/development/rfc/ms-rfc-67.html.

RFC does not take into account all possible combinations to use the enable/disable rules at MAP and LAYER level. It seems that you have found one way to configure Mapserver so that it is not compliant to WMS standard and there may be more. I suggest to analyze the situation and make a bug report or feature request for new checks. The concrete bug, I guess, is that disabling GetMap removes the GetMap operation from GetCapabilities while it should keep  the operation, which is mandatory, but hide all the layers.

I guess that you can make Mapserver behave correctly by using  "wms_enable_request" "GetCapabilities GetMap" at the map level and by hiding all the layers with "!*", except for the layers you want to stay available.

-Jukka Rahkonen-





-----Alkuperäinen viesti-----
Lähettäjä: mapserver-users [mailto:[hidden email]] Puolesta Jörg Thomsen (WhereGroup)
Lähetetty: 7. joulukuuta 2017 16:36
Vastaanottaja: [hidden email]
Aihe: Re: [mapserver-users] wms_enable_request header vs. layer

Moin,

I think the problem is, that the Layers allow the GetMap-Request and MapServer does not provide the required Information in the capabilities.

Am I wrong?

Jörg



Am 07.12.2017 um 11:30 schrieb Passmore, James H.:> Technically QGIS (or any other client) is going against the WMS standard by requesting something not in GetCapabilities response, and MapServer is at fault for responding with something not advertised.

>
> Of course a GetMap operation is mandatory for a WMS, so you might argue that MapServer is at fault for providing a GetCapabilities response that doesn't advertise a GetMap operation.
>
> James
>
> -----Original Message-----
> From: mapserver-users [mailto:[hidden email]]
> On Behalf Of [hidden email]
> Sent: 06 December 2017 20:00
> To: [hidden email]
> Subject: mapserver-users Digest, Vol 119, Issue 5
>
> Send mapserver-users mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific than "Re: Contents of mapserver-users digest..."
>
>
> Today's Topics:
>
>    1. wms_enable_request header vs. layer (Jörg Thomsen (WhereGroup))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 6 Dec 2017 13:41:36 +0100
> From: Jörg Thomsen (WhereGroup)  <[hidden email]>
> To: "[hidden email]"
> <[hidden email]>
> Subject: [mapserver-users] wms_enable_request header vs. layer
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> I need an explanation for ows_enable_request.
>
> There are two mapfiles, brw_enable_header.map and brw_enable_layer.map The only difference is, that in brw_enable_header.map I have enabled all ows requests within the metadata-section in the header and in each layer.
>
> In brw_enable_layer.map I only have enabled all requests in the layer-section, but not in the header.
>
> Both WMS allow the capability-request and in brw_enable_layer.map the information for the wms-request is missing:
> https://www.diffchecker.com/KjsX2Wbk
>
> OK. The brw_enable_layer.map (with no ows_enable_reqeust in the header) allows GetMap-Requests:
> http://h2743629.stratoserver.net/cgi-bin/mapserv?map=/data/ows/map/brw
> _enable_layer.map&&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=48.60
> 086340827337636,9.02229999999999954,48.65160000000000196,9.07331344424
> 46044&CRS=EPSG:4326&WIDTH=426&HEIGHT=422&LAYERS=bodenrichtwertzone&STY
> LES=&FORMAT=image/png&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96&T
> RANSPARENT=TRUE
>
> I think this is technically correct, but as the capabilities don't provide any information for the getMap-Request (no online-ressource, no image-formats), a client does not know this parameters. In the result I cannot load the WMS into a mabpender-application.
> I wonder why (and I am surprised) QGIS doesn't have any problems with this wms.
>
> Is this how it shall be? Is MapServer working correct or Mapbender? Or both, but ...?
>
> Regards, Jörg
>
> --
>
> ***********************************
> Where2B Konferenz 2017
> 14. Dezember 2017 in Bonn
> www.where2b-conference.com
> ***********************************
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> mapserver-users mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
> ------------------------------
>
> End of mapserver-users Digest, Vol 119, Issue 5
> ***********************************************
> ________________________________
>  This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
> ________________________________
> _______________________________________________
> mapserver-users mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>


Viele Grüße,
Jörg Thomsen

--

***********************************
Where2B Konferenz 2017
14. Dezember 2017 in Bonn
www.where2b-conference.com
***********************************

Jörg Thomsen
WhereGroup GmbH & Co. KG
Gillweg 3
14193 Berlin
Germany

Fon: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 89 09 53 21

[hidden email]
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
-------------------------------
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
-------------------------------
Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com _______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
mapserver-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-users