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:[email protected]] On 
Behalf Of [email protected]
Sent: 06 December 2017 20:00
To: [email protected]
Subject: mapserver-users Digest, Vol 119, Issue 5

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

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
[email protected]

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

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)  <[email protected]>
To: "[email protected]"
<[email protected]>
Subject: [mapserver-users] wms_enable_request header vs. layer
Message-ID: <[email protected]>
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
[email protected]
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
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to