[
https://issues.apache.org/jira/browse/SOLR-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621820#comment-15621820
]
Shalin Shekhar Mangar commented on SOLR-9188:
---------------------------------------------
bq. Can we please leave this JIRA as fixed in 6.2.1 and close this? Then do the
fix of regression bugs in SOLR-9692 in 6.3? This CHANGES history rewrite is
just confusing in my eyes.
+1. Issues once resolved and fixed should not be opened and new jira should be
used for further work. Please return this issue to its former state i.e. fixed
as of 6.2.1. Please do not rewrite CHANGES.txt as it is not a living document.
It is part of every release artifact as well as archived on the site e.g.
https://lucene.apache.org/solr/6_2_1/changes/Changes.html. If you want, you can
mention this issue as part of the CHANGES.txt in 6.3 saying that SOLR-9188 did
not fix the issue as stated in 6.2.1
> BlockUnknown property makes inter-node communication impossible
> ---------------------------------------------------------------
>
> Key: SOLR-9188
> URL: https://issues.apache.org/jira/browse/SOLR-9188
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 6.0
> Reporter: Piotr Tempes
> Assignee: Noble Paul
> Priority: Critical
> Labels: BasicAuth, Security
> Fix For: 6.3, master (7.0)
>
> Attachments: SOLR-9188.patch, solr9188-errorlog.txt
>
>
> When I setup my solr cloud without blockUnknown property it works as
> expected. When I want to block non authenticated requests I get following
> stacktrace during startup (see attached file).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
