2008/11/25 Brian E. Fox <[EMAIL PROTECTED]> > The central repo has been undergoing significant load lately,
<snip /> > Also, if you are using a repo manager, make sure to correctly configure > it to not make requests to public repositories for your internal > artifacts. Otherwise you are making a ton of requests for things that > will never be found, increasing the bandwidth usage on your side and > ours. Also it gives away potentially sensitive information as someone > could scrape the logs and figure out what you're up to internally based > on these requests. Nexus lets you configure routing rules so you could > exclude com.yourcompany.* from central. Archiva has similar > functionality, I'm not sure about Artifactory. > Hi Brian, We've configured an internal maven repository manager some months ago for now. So, our requests should not be too high on the repo1.maven.org. But as we might have missed something in the configuration, wouldn't be possible to access logs from central in some way? I mean, I know there would some privacy/security problems to do that without any restrictions. But maybe those logs could be filtered by the requesting (public) IP? This way, it would be possible for us to know if our hit count is acceptable or not according to say some typical/acceptable value you would provide? I know you all already have enough work with maven not to look for new tasks :-). Just wanting to detect my potential MRM leakages :-) (or inside developers that would directly hit central without going through our internal repo/proxy...). Cheers. -- Baptiste <Batmat> MATHUS - http://batmat.net Save a tree, Eat a beaver!
