WordPress.org
Get WordPress

Plugin Directory

Changeset 1506266


Ignore:
Timestamp:
10/01/2016 04:58:53 AM (10 years ago)
Author:
gnotaras
Message:

Updated readme.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • reverse-proxy-comment-ip-fix/trunk/readme.txt

    r1382601 r1506266  
    11=== Reverse-Proxy Comment IP Fix ===
    22Contributors: gnotaras
    3 Donate link: http://www.g-loaded.eu/about/donate/
    4 Tags: reverse-proxy, x-forwarded-for, proxy, server, comments
     3Tags:
    54Requires at least: 1.5.2
    65Tested up to: 4.5
    76Stable tag: 0.2.0
    87License: Apache License v2
    9 License URI: http://www.gnu.org/licenses/gpl-3.0.txt
    108License URI: http://www.apache.org/licenses/LICENSE-2.0.txt
    119
    … …  
    1715Sets the comment IP to the client IP provided by the X-Forwarded-For or X-Real-IP headers before the comment is saved to the database.
    1816
     17Note: Please note that the existence of trustworthy information in the `X-Forwarded-For` and the `X-Real-IP` HTTP headers is up to the system administrator. HTTP clients can send HTTP headers containing invalid information. It is highly recommended to reset these headers at the first web proxy server you trust.
     18
     19**NOTICE:** THIS PLUGIN HAS BEEN **DEPRECATED**. IT IS NO LONGER SUPPORTED. IT IS NO LONGER TESTED WITH NEW WORDPRESS RELEASES. USING IT IN PRODUCTION IS NOT RECOMMENDED.
     20
     21IT IS STRONGLY SUGGESTED TO MIGRATE TO OTHER MORE MODERN AND BETTER MAINTAINED PLUGINS.
     22
     23IF YOU ARE STARTING A NEW BLOG, IT IS HIGHLY RECOMMENDED TO SEARCH FOR OTHER PLUGINS IN ORDER TO AVOID THE INEVITABLE FUTURE MIGRATION.
     24
     25REGARDING EXISTING USERS, AT THE TIME OF WRITING, THERE ARE NO MAJOR BUGS. PROVIDED THAT THE WORDPRESS API DOES NOT CHANGE SOON, YOU HAVE THE TIME TO EXPERIMENT WITH OTHER PLUGINS AND PLAN YOUR MIGRATION.
     26
     27<blockquote>
     28
     29<strong>Important Notice</strong>
     30
     31<br /><br />
     32
     33I have stopped using this plugin and therefore I won't be supporting it or testing it with any new WordPress releases in the future. I highly recommend switching to a mechanism that is specific to your web server in order to do what this plugin does. Please check your web server's documentation or community support forums for more information. Please note that by continuing using this plugin you are on your own.
     34
     35<br /><br />
     36
     37</blockquote>
    1938
    2039= Official Project Homepage =
    … …  
    3049== Frequently Asked Questions ==
    3150
    32 = Does this just work? =
     51= Does this plugin just work? =
    3352
    34 Yes.
     53Yes. After activation, there are no more configuration steps.
     54
     55= How can the plugin determine that the client IP address contained in the `X-Forwarded-For` and the `X-Real-IP` HTTP headers is the real one? =
     56
     57It can't. There is no way that the plugin can make any decision about whether the information contained in the `X-Forwarded-For` and the `X-Real-IP` HTTP headers is real or not. This decision has to be taken by the system administrator. The general idea is that the first trusted web proxy should be configured in such a way so that these headers are reset at that point and thereafter contain only information the system administrator trusts.
     58
     59= Are there any alternative ways to set the client's real IP address in the REMOTE_ADDR server variable? =
     60
     61Although this question is outside the scope of this FAQ, indeed, this can be done. If your web server is *Apache*, you can use one the following modules: [mod_remoteip](http://httpd.apache.org/docs/2.4/mod/mod_remoteip.html) (httpd >= 2.4), [mod_rpaf](https://github.com/gnif/mod_rpaf), [mod_extract_forwarded](http://www.openinfo.co.uk/apache/). In case you use *Nginx*, check the [ngx_http_realip_module](http://nginx.org/en/docs/http/ngx_http_realip_module.html).
     62
     63All these modules can extract the client's IP address from user-defined HTTP headers and update the `REMOTE_ADDR` server variable. In that case, this plugin is no longer needed in your WordPress installation, as the real IP address of the client is directly available in the server variables.
     64
     65= Do you use this plugin? =
     66
     67This plugin has been deprecated.
     68
    3569
    3670== Changelog ==
     71
     72**NOTICE:** THIS PLUGIN HAS BEEN **DEPRECATED**. IT IS NO LONGER SUPPORTED. IT IS NO LONGER TESTED WITH NEW WORDPRESS RELEASES. USING IT IN PRODUCTION IS NOT RECOMMENDED.
     73
     74IT IS STRONGLY SUGGESTED TO MIGRATE TO OTHER MORE MODERN AND BETTER MAINTAINED PLUGINS.
     75
     76IF YOU ARE STARTING A NEW BLOG, IT IS HIGHLY RECOMMENDED TO SEARCH FOR OTHER PLUGINS IN ORDER TO AVOID THE INEVITABLE FUTURE MIGRATION.
     77
     78REGARDING EXISTING USERS, AT THE TIME OF WRITING, THERE ARE NO MAJOR BUGS. PROVIDED THAT THE WORDPRESS API DOES NOT CHANGE SOON, YOU HAVE THE TIME TO EXPERIMENT WITH OTHER PLUGINS AND PLAN YOUR MIGRATION.
    3779
    3880Please read the dynamic [changelog](http://www.codetrax.org/projects/reverse-proxy-comment-ip-fix/roadmap "Reverse-Proxy Comment IP Fix ChangeLog")
Note: See TracChangeset for help on using the changeset viewer.