On Fri, Jan 14, 2011 at 2:49 PM, Chris Holmes <[email protected]> wrote: > I definitely agree that we should protect the capabilities document. Though > I think this is not normally an issue because if anyone tries to configure > something that doesn't work then GeoServer doesn't let you. So the only > ones that can get in are when the data directory is misconfigured from the > start. Like I wouldn't be able to add in the faulty pk50095 layer. > > So for the immediate term (like RC1) let's disable pk50095. People can > choose to enable it if they want, but then by default we're not giving bad > capabilities documents in tomcat.
Works for me Cheers Andrea -- Ing. Andrea Aime Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
