[mapserver-users] [TinyOWS] Broken config using a MAPFILE?

[Olivier Courtin]

Hi Jukka,



> > But as you could seen, a bit less with GET request !
>
> Somehow I feel this is a bug.
>
> > Could worth to open a ticket, to be more strict on GET Namespace.
> But how strict it should be? Should we learn users to include the correct
> namespace always in the typeName? It is correct but most users do not care
> about namespaces and they could feel that frustrating. And I suppose that
> the colon character needs to be escaped at least inside filters for making
> the GET requests to work and that makes things more complicated. However,
> it is possible that the same TinyOWS service has both foo:parcels and
> bar:parcels.
>

NAMESPACE parameter is not Mandatory with GET request,
(and very few clients use it) so as you said not the right way to handle it.

But on the other side we have the ns_prefix value associated with
every layer, so we could at least check if it match yes or no.

-- 
Olivier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20120919/56ffbb48/attachment.html>