Scott Phillips wrote: > We wanted to expose dspace's metadata in a way that can be used by > other applications. They are nice restfull urls that are actionable > and easily predictable.
In most cases, that should be seen as a good thing. I can see in certain situations that you wouldn't want to expose that publicly though. So, in the interests of furthering our collective knowledge, I'll pose the question for tackling it another way - is it possible to restrict what has access to the /metadata urls? (ie. by IP address). If you can restrict part of the url space to only being accessible either from an internal Cocoon resolution and/or specific IP addresses (ie. 127.0.0.1), then you can prevent leakage of [sensitive] information, whilst still allowing the internal processes, your own debugging, and possibly even 'trusted partners' access to the data they need. G This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
