[
https://issues.apache.org/jira/browse/SOLR-18537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126528#comment-18126528
]
David Smiley commented on SOLR-18537:
-------------------------------------
It'd be nice to eventually remove the existing custom functionality in lieu of
this. That'd mean changing the consumers first (admin UI), and deprecate the
functionality Solr side. I am attaching Claude's analysis of doing that
transition.
> 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
> Attachments: response.md
>
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
