[
https://issues.apache.org/jira/browse/TS-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150028#comment-15150028
]
Christoph Keller commented on TS-4204:
--------------------------------------
I'm still thinking about how to implement that.
- core or plugin?
- is it sufficient to replace the client-ip mime-header?
- what should TSHttpTxnIncomingAddrGet return?
- would it be best to just keep everything as it is and just add a function
like TSHttpTxnIncomingXffAddrGet to api?
- is it necessary to keep imcomingaddr?
Any thoughts on that?
If nobody is already working on this i probably will.
> Plugin similar to remoteip
> --------------------------
>
> Key: TS-4204
> URL: https://issues.apache.org/jira/browse/TS-4204
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Christoph Keller
> Priority: Minor
> Fix For: sometime
>
>
> Would be nice if there was some kind of plugin which handles all that
> x-forwarded-for stuff. I'm thinking of something like this ->
> https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html
> It just replaces the clientip with the first untrusted ip in
> x-forwarded-for-header or whatever header is configured. Plugins loaded after
> it could just use clientip for any ip based processing instead of
> implementing that all on their own.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
