[
https://issues.apache.org/jira/browse/SOLR-18537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136779#comment-18136779
]
David Smiley commented on SOLR-18537:
-------------------------------------
There's a related security matter I'll volunteer for, somewhat begrudgingly
LOL. Next deprecate the "nodes" param (if I have that correct, as implemented
by AdminHandlersProxy) on handlers that do this sort of proxying, for removal
in Solr 11. The admin UI can shift over to this mechanism in lieu of the
"nodes" param.
> Proxy to any user-specified SolrCloud node by header/param
> ----------------------------------------------------------
>
> Key: SOLR-18537
> URL: https://issues.apache.org/jira/browse/SOLR-18537
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Attachments: response.md
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> It can be very useful for Solr to proxy requests to another node, specified
> in a header or param. The intended scenario is when there's an HTTP proxy in
> front of Solr, and the backing Solr nodes aren't directly reachable. Solr is
> doing that now for a few admin endpoints that have already been coded for it,
> using {{GenericV1RequestProxy}} internally (e.g. for logging, info, ...).
> The issue here instead proposes a generic mechanism that doesn't require Solr
> handlers to be coded any differently.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
