On Wed, 2011-06-22 at 11:40 -0700, Jamie Popkin wrote:
> Hello all.
> 
> I've found that it's not possible to seed the cache of a secure layer.
> Even when properly authorized. The workaround is to make they layer
> temporarily public... Seed the cache.... Then securing the layer when
> it's done. Obviously this isn't ideal.
> 
> 
> Does anyone know why this is? I'm guessing the threads used to seed a
> cache run with a different permission set.... Yet not sure.
> Has anyone else run into this issue? 
What geoserver version are you using? I'm not completely sure but I
guess 2.1.0 and 2.1.1 (hopefully coming out this week) will suffer the
same defect, which is fixed on trunk. Sorry if it didn't make it to the
latest stable release.

> 
> 
> Thanks
> Jamie
> 
> 
> --
> Jamie Popkin
> Little Earth
> @jamiepopkin
> http://littleearth.ca
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> _______________________________________________ Geoserver-users mailing list 
> [email protected] 
> https://lists.sourceforge.net/lists/listinfo/geoserver-users

-- 
Gabriel Roldan
[email protected]
Expert service straight from the developers


------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to