Hi Steve, Yes that is pretty much it. As you can see from the branch there are minimal changes, and provides a "canonical" URL for all OGC services. I'll make a pull request next week and update the relevant tests.
Seth -- web:https://geographika.net twitter: @geographika On Mon, Mar 6, 2023, at 11:39 PM, Steve Lime wrote: > Hmmm... so if path_info contains exactly one value, use it for the map= > value. I could get behind that. Nice and clean. > > On Mon, Mar 6, 2023 at 7:22 AM Seth G <[email protected]> wrote: >> Hi devs, >> >> The OGC Features API introduced in MapServer 8.0 allows accessing Mapfiles >> using keys in the config file: >> >> URL: http://example.com/mykey/ogcapi/collections/foo/items. >> Config file: >> >> CONFIG >> MAPS >> mykey "/path/to/mapfile" >> END >> END >> >> For all other requests you have to use the format >> http://example.com/?map=mykey&request=WMS... >> >> I think it would be nice to be able to use the same approach as OGC Features >> API to allow the key to be used as part of the URL e.g. a WMS request could >> be accessed using: http://example.com/mykey/?request=WMS... >> >> The changes to allow this seem to be minimal (with work to be done on tests >> and docs) - see [1] >> >> Does anyone have any thoughts or reservations on adopting this approach? >> >> Seth >> >> [1] >> https://github.com/MapServer/MapServer/compare/main...geographika:mapserver:mapfile-key-url >> >> >> -- >> web:https://geographika.net >> twitter: @geographika >> _______________________________________________ >> MapServer-dev mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
_______________________________________________ MapServer-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-dev
