[
https://issues.apache.org/jira/browse/FLUME-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702260#comment-14702260
]
Evgeny Minkevich commented on FLUME-2764:
-----------------------------------------
Thank you for responding that quickly.
Not sure that it would work. The idea I was playing with was to combine it with
a multiplexing selector to decide into which channel the message should go -
and, eventually, Kafka topic.
So while the URI is indeed semi-rigid, there still a degree of variation is
expected.
> HTTPSource saving client ip and some http-headers into event
> ------------------------------------------------------------
>
> Key: FLUME-2764
> URL: https://issues.apache.org/jira/browse/FLUME-2764
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Reporter: dima levchenko
> Labels: features, newbie, patch
> Attachments: flume-2764-0.patch
>
>
> I plan to use flume as a receiver of events coming from javascript
> applications. For each event I would like to store an IP from which this
> event comes. Because flume can be behind some proxy, I also would like to be
> able to retrieve original IP from headers set by this proxy.
> this behavior seems pretty common for http components, so I would like to
> suggest an improvement for HTTPSource to dump remote ip, and/or some headers
> into event headers.
> thank you for comments :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
