Solr tests will all completely fail in that case then: just like they do when i run them on my laptop with internet disconnected.
thats because it looks up its own hostname: which involves reverse/forward dns lookups. On Mon, Sep 16, 2013 at 1:07 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : the main problem with any security manager is: To check if a connection > : is allowed, it has to resolve DNS and look the IP up in the policy. > > Can we update the secuity policy to fail fast anytime a DNS lookup > happens? even if it happens implicitly in situations like this > (URL.hashCode) so we can more easily find problems like this via test > Exceptions instead of via slow tests? > > (I'm not saying it's a good idea to do this -- i don't know -- it might > make more trouble then it's worth ... i'm just trying to udnerstand if > it's possible) > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org