You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jspwiki.apache.org by "Juan Pablo Santos Rodríguez (JIRA)" <ji...@apache.org> on 2013/11/28 21:06:35 UTC

[jira] [Resolved] (JSPWIKI-804) SpamFilter should support X-Forwarded-For header in the banlist

     [ https://issues.apache.org/jira/browse/JSPWIKI-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juan Pablo Santos Rodríguez resolved JSPWIKI-804.
-------------------------------------------------

    Resolution: Fixed

done in 2.10.0-svn-48

> SpamFilter should support X-Forwarded-For header in the banlist
> ---------------------------------------------------------------
>
>                 Key: JSPWIKI-804
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-804
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Filters
>    Affects Versions: 2.10
>         Environment: NA
>            Reporter: Harry Metske
>            Assignee: Harry Metske
>             Fix For: 2.10
>
>
> Currently the SpamFilter only supports banning based on IP address of the client (as gotten from the HttpRequest.getRemoteAddr() ).
> If you are behind a proxy or loadbalancer, chances are that you get the address of the proxy or lb instead of the real client IP address.
> Therefore the X-Forwarded-For request header could be used.
> See http://en.wikipedia.org/wiki/X-Forwarded-For



--
This message was sent by Atlassian JIRA
(v6.1#6144)