Also, I’d say that any perceived extra security by not having this info in the response is not really security, just security theatre.
Keep it in. Michael Smith US Army Corps > On Feb 16, 2022, at 6:34 AM, Tom Kralidis <[email protected]> wrote: > > > I would suggest keeping at least the version somewhere in the responses (i.e. > current behaviour, or > move to an HTTP header). For scenarios where users do not have access to the > deployment environment, > this information is critical. > > ..Tom > >> On Tue, Feb 15, 2022 at 8:49 PM Steve Lime <[email protected]> wrote: >> What do folks think about dropping the version output from MapServer? That >> is, output like: >> >> <!-- MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG SUPPORTS=PROJ >> SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=ICONV >> SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER >> SUPPORTS=WCS_SERVER SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG >> INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE --> >> I'm not sure that advertising version and supported components makes sense >> anymore. Might be able to make it tunable via the config file but I'm not >> sure that's even necessary. >> >> --Steve >> _______________________________________________ >> 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
_______________________________________________ MapServer-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-dev
