Problems with mime type in WMS capabilities request

[Bart van den Eijnden]

Hi,

there is no way to control it since it required by the OGC specification
(at least WMS 1.1.X), except for changing the source code and recompile.
Or use &version=1.0.7 instead.

Those other services are not fully OGC complaint, since the spec states
you have to use application/vnd.ogc.wms_xml for a GetCapabilities
response. See also:

http://cite.occamlab.com/test_engine/wms_1_1_1/files/wms_assertions/

testcase: "ms/wmsops/getcapabilities/response/1"

When a GetCapabilities request is made, then the content-type header of
the response is application/vnd.ogc.wms_xml

Best regards,
Bart

On Fri, 11 Mar 2005 18:06:01 +0000, Nuno GIL <nunoragil at gmail.com> wrote:

> Hi,
> But is there any way of controlling the capabilities output mime type
> in MapServer?
> If I test other services, also WMS 1.1 compliant, their capabilities
> document is automatically show on the browser...
> Thanks in advance,
> Nuno
>
>
> On Fri, 11 Mar 2005 18:14:35 +0100 (CET), bartvde at xs4all.nl
> <bartvde at xs4all.nl> wrote:
>> Hi Nuno,
>>
>> this was something introduced by OGC in WMS spec 1.1, they invented
>> their
>> own mime types, but ofcourse no single browser interprets things like:
>> application/vnd.ogc.se_xml.
>>
>> In WMS 1.3 they have changed the MIME type for capabilities back to
>> text/xml AFAIK.
>>
>> Best regards,
>> Bart
>>
>> > Dear Listers,
>> > When I request a getcapabilites from our server
>> >
>> (http://iceds.ge.ucl.ac.uk/cgi-bin/wms?map=wms.map&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetCapabilities),
>> > the capabilities file type that is returned is not recognized as XML
>> > and not displayed immediately on the browser... To go around this I
>> > simply rename the file adding an XML extension to it. This may have to
>> > do with a wrong mimetype configuration...
>> > Any ideas how to sort this out?
>> > Regards,
>> > Nuno
>> >
>>
>>
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/