[
https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476833#comment-16476833
]
ASF GitHub Bot commented on NIFI-4198:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2094
@mattyb149 I was able to use a Proxy server with basic authentication
without issue. I wonder if your Nginx can be used as a forward proxy. Nginx is
generally used as a reverse proxy which resides on the server side and routes
incoming client requests into backend server applications. While forward proxy
tends to be in the client side network to go through company firewall ... etc.
https://stackoverflow.com/questions/46060028/how-to-use-nginx-as-forward-proxy-for-any-requested-location
@arunma The code LGTM, except, I believe the proxy username/password
property descriptor should support variable registry EL. I'm going to add EL
support and merge this. Thanks!
> *ElasticsearchHttp processors do not expose Proxy settings
> ----------------------------------------------------------
>
> Key: NIFI-4198
> URL: https://issues.apache.org/jira/browse/NIFI-4198
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Andre F de Miranda
> Assignee: Arun Manivannan
> Priority: Major
> Attachments: NIFI-4198-ElasticProxy-TestFixtures.pdf,
> NIFI-4198-ElasticProxy.xml
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
