On Tue, Mar 15, 2016 at 3:29 PM, Andrea Aime <[email protected]>
wrote:
> By the way, the usage of "ows" in the caps documents has been ignored for
> so much time that I guess it could
> be put on the discussion table again. I have no strong opinion on the
> matter, to GeoServer wms/wcs/wps/ows
> are all the same (you can literally use geoserver/workspace/wms to make a
> wfs request if you want to,
> unless you're forgetting to add &service=WFS in the URL it should not make
> any difference).
> E.g.:
>
>
> http://demo.geo-solutions.it/geoserver/tiger/wms?service=WFS&version=1.0.0&request=GetFeature&typeName=tiger:tiger_roads&maxFeatures=50
>
> And oh, noticed that the preview is indeed using "ows" for WFS, but "wms"
> for WMS preview links... LOL :-)
>
Yes, it would be nice to have that discussion about the service endpoints.
Although the current behavior provides a lot a flexibility (simply by
adding the appropriate "&service=XYZ"), it makes things messy and not very
logical in my opinion.
A concrete example of where this is an issue, is when trying to limit
access to specific protocols, when GeoServer is running behind a reverse
proxy.
But as you said that the "correct" endpoint URL is "/ows?SERVICE=XYZ&",
that means that such a reverse proxy would have to check the query
parameters anyway.
--
*Damiano Albani*
Geodan
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
