fabien cellier <fabien.cell...@...> writes: > It's depend on what you want. If it's just blocking request which are > not in a certain boundingbox for a certain user, it's very easy thanks > acegi,spring and the > org.geoserver.ows.security.OperationInterceptor (if you want know how > it's works, you can read org.geoserver.ows.Dispatcher#execute in ows > module).
Great ! Thanks. > Nevertheless, if you want rewrite response (for example having picture > with information only in the permitted Bbox), it's harder, you have to > rewrite a part of response's writer (perhaps another solution exist but > I haven't found it :() That would be nice too... but not a must on the project I am working on. Could you share the details on how you extended the security configuration files to put in them the info about the allowed bbox ? Regards, ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
