[wfs-dev] Re: how to advertize HTTP Post in WFS capabilities?

[Martin Daly]

Bart,

You're right, both options are valid.  Quite aside from whether or not
this is sensible, we'll fix it in SIS.

Regards,
Martin

> Hi list,
> 
> while testing a Mapserver WFS against a Cadcorp SIS 
> Mapbrowser I ran into
> the following issue:
> 
> In its capabilities Mapserver is trying to say that is 
> supports HTTP POST,
> eg:
> 
>     <DCPType>
>         <HTTP>
>           <Get
> onlineResource="http://myserver/cgi-bin/mapserv.exe?map=/ms4w/
> apps/general/map/world.map&amp;"
> />
>         </HTTP>
>       </DCPType>
>       <DCPType>
>         <HTTP>
>           <Post
> onlineResource="http://myserver/cgi-bin/mapserv.exe?map=/ms4w/
> apps/general/map/world.map&amp;"
> />
>         </HTTP>
>       </DCPType>
> 
> So it uses a new DCPType element for GET and POST.
> 
> Cadcorp SIS Mapbrowser says that the Mapserver WFS does not 
> support HTTP
> POST. Apparently it expects something like:
> 
>     <DCPType>
>         <HTTP>
>           <Get
> onlineResource="http://myserver/cgi-bin/mapserv.exe?map=/ms4w/
> apps/general/map/world.map&amp;"
> />
>                     <Post
> onlineResource="http://myserver/cgi-bin/mapserv.exe?map=/ms4w/
> apps/general/map/world.map&amp;"
> />
>         </HTTP>
>       </DCPType>
> 
> So only 1 DCPType element for the POST and GET.
> 
> Both options are valid according to the schema!
> 
> IMHO it would be better to limit one of these options by the spec. Any
> thoughts?
> 
> Best regards,
> Bart