On Thu, Feb 21, 2013 at 3:42 PM, Christian Mueller <[email protected]> wrote: > Fine, but be aware of the fact that each new cookie creates an HTTP session > on the Geoserver side wasting resources you do not need for WMS requests. At > the end of the day, it is your decision :-) > > Christian >
Christian the point is that I need to add a WMS layers in Leaflet, and I do not see an easy way to modify headers using the Leaflet WMS class [1]. Neither I wish to expose username and password as suggested here [2] at the client side (this solution does not work for all browser, though, as far as I can see). By the way: is there any available complete OpenLayers example performing Basic Authentication with WMS? I couldn't find one. That is why I have been looking to a way to perform cookie authentication, modifying the response with Python and attaching the cookie to the response (using Django here). Unluckily this approach does not work if the GeoServer and Web App domains are different, as the generated cookie won't be accepted by GeoServer (while the JSESSIONID has a valid value, the domain is different), and this is the scenario I am in. I am looking now to alternatives, but I am afraid that using proxies or cascading or extending Leaflet are the only options here. thanks for your kind support p [1] http://leafletjs.com/reference.html#tilelayer-wms [2] http://osgeo-org.1560.n6.nabble.com/Load-GeoServer-WMS-secured-layers-with-OpenLayers-td3919938.html -- Paolo Corti Geospatial software developer web: http://www.paolocorti.net twitter: @capooti skype: capooti ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
