[mapserver-users] MapServer requires unnecessary SERVICE=WMSparameter in GetMap request

[Jan Hartmann]

Meanwhile, the easiest solution for those using 5.0-5.2.0 is adding 
"service=wms" to the onlineresource string in the metadata section of 
the mapfile, as documented in

http://trac.osgeo.org/mapserver/ticket/1262

Jan

Paul Ramsey wrote:
> Arg, it was indeed. My cursory trac search didn't turn it up :(
>
> http://trac.osgeo.org/mapserver/ticket/2737
>
> I'll close out that new ticket.
>
> P
>
> On Mon, Dec 22, 2008 at 3:15 PM, Steve Lime <Steve.Lime at dnr.state.mn.us> wrote:
>   
>> I thought 5.2.1 fixed this already?
>>
>> Steve
>>
>>     
>>>>> On 12/22/2008 at 5:13 PM, in message
>>>>>           
>> <30fe546d0812221513i32dc690dn703d65111f59080a at mail.gmail.com>, "Paul Ramsey"
>> <pramsey at cleverelephant.ca> wrote:
>>     
>>> Right you are, another hidden gem of the specification... I've
>>> assigned a ticket to this. It seems pretty important to my mind, so if
>>> others are busy, I'll fix it.
>>>
>>> http://trac.osgeo.org/mapserver/ticket/2839
>>>
>>> P.
>>>
>>> On Mon, Dec 22, 2008 at 2:25 PM, John Maurer <maurerj at nsidc.org> wrote:
>>>       
>>>> Dear MapServer users,
>>>> I recently discovered that MapServer (we are using 5.2.0) requires a SERVICE
>>>> parameter (i.e. SERVICE=WMS) in a GetMap OGC request even though this
>>>> parameter is not mentioned or required in the WMS 1.1.1 OGC specification
>>>> for GetMap requests:
>>>>
>>>> http://www.opengeospatial.org/standards/wms
>>>>
>>>> It is strange that this is so since GetFeature and GetCoverage both require
>>>> the SERVICE paramter, but for whatever reason the GetMap spec doesn't. Kind
>>>> of an inconsistency in the OGC services, but MapServer needs to abide by it.
>>>>
>>>> This cropped up when a user contacted me that our WMS services were not
>>>> working in ArcGIS 9.2 after we upgraded MapServer from 4.9 to 5.2. After
>>>> discussion with ESRI, they pointed out that MapServer was throwing an error
>>>> about a missing SERVICE parameter because they do not include this parameter
>>>> in their GetMap requests. However, the SERVICE parameter should not be
>>>> required according to the spec.
>>>>
>>>> I modified our CGI to fill this parameter in by default if not provided as a
>>>> workaround, but a future release of MapServer should probably remove the
>>>> requirement for this parameter in GetMap requests. Or am I missing something
>>>> (always a possibility!)? Thanks!
>>>> Cheers,
>>>>
>>>> --
>>>> John Maurer
>>>> Web/Database Applications Engineer
>>>> National Snow and Ice Data Center (NSIDC)
>>>> University of Colorado at Boulder
>>>> http://cires.colorado.edu/~maurerj
>>>> +1-303-586-1677
>>>> ------------------------------------
>>>> "Without geography, you're nowhere!"
>>>>
>>>>
>>>> _______________________________________________
>>>> mapserver-users mailing list
>>>> mapserver-users at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>>>>
>>>>         
>>> _______________________________________________
>>> mapserver-users mailing list
>>> mapserver-users at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>>>       
>>     
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapserver-users/attachments/20081223/e9c87140/attachment-0001.html