[mapserver-dev] Cookies as Params

Michael Smith michael.smith.erdc at gmail.com
Fri Sep 24 12:19:31 PDT 2021



This is something we do a lot. We pass authentication set internally as cookies. If this went again, we’d be seriously impacted. 






Michael Smith

US Army Corps / Remote Sensing GIS Center




From: MapServer-dev <mapserver-dev-bounces at lists.osgeo.org> on behalf of Steve Lime <sdlime at gmail.com>
Date: Friday, September 24, 2021 at 2:32 PM
To: MapServer Dev Mailing List <mapserver-dev at lists.osgeo.org>
Subject: [mapserver-dev] Cookies as Params


Hi all: MapServer has always treated cookies as parameters. Those values are added to the parameter names and values arrays and are basically just another way to set standard request parameters. This can cause a problem with OGC API specs that require exceptions be generated when unexpected parameters are encountered. Note that standard AJAX use with something like jQuery can also trigger the exception when it tags on params to make calls unique - so there's more to discuss.


Anyway, it got me wondering if we need to continue to handle cookies at all. I don't see much value and simpler is better but I don't know if others might be using that feature... Thoughts?



_______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20210924/16d72282/attachment.html>

More information about the MapServer-dev mailing list