You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2015/08/26 20:00:46 UTC

[jira] [Commented] (SOLR-7977) SOLR_HOST in solr.in.sh doesn't apply to Jetty's host property

    [ https://issues.apache.org/jira/browse/SOLR-7977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715243#comment-14715243 ] 

Shawn Heisey commented on SOLR-7977:
------------------------------------

I don't think that property was initially intended to be applicable to Jetty.  It's how the hostname gets overridden for SolrCloud.

I can envision situations where the host that the user wants to include in zookeeper is entirely different from the host they want to use for network binding.


> SOLR_HOST in solr.in.sh doesn't apply to Jetty's host property
> --------------------------------------------------------------
>
>                 Key: SOLR-7977
>                 URL: https://issues.apache.org/jira/browse/SOLR-7977
>             Project: Solr
>          Issue Type: Bug
>          Components: security, SolrCloud
>            Reporter: Shalin Shekhar Mangar
>              Labels: impact-medium
>             Fix For: Trunk, 5.4
>
>
> [~sdavids] pointed out that the SOLR_HOST config option in solr.in.sh doesn't set Jetty's host property (solr.jetty.host) so it still binds to all net interfaces. Perhaps it should apply to jetty as well because the user explicitly wants us to bind to specific IP?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org