This modification has been withdrawn.
vBulletin 4.0.x and 4.1.x are no longer supported.
For vBulletin 4.2.x please use the built in reverse proxy detection.
Problem the built in vbulletin reverse proxy detection is based on a list of IP to reverse
So if there are hundreds thousands IP to reverse the server will search for a match whenever any user does anything, and I'm afraid that's certain death for the server
However, as of 4.2.3 a couple of new options were added to the core to help in this case.
Code:
/* Enter your known proxy servers here. You can list multiple trusted IPs separated by a comma.
You can also use the * wildcard (at the end of a definition only) or use the keyword 'all' to represent any ip address.*/
//$config['Misc']['proxyiplist'] = '127.0.0.1, 192.168.*, all';
Also, in 4.2.4 an extra fix was added due to PHP sometimes not passing the custom headers into the $_SERVER array (which stopped the system working).
wow, completely missed this as I took the bad habit of not updating the config file anymore :O
thank you, works fine
Always update the config.php file using config.php.new, just copy/paste the values then save and overwrite . In some cases issues can arise form using an older config.php file.
However, as of 4.2.3 a couple of new options were added to the core to help in this case.
Code:
/* Enter your known proxy servers here. You can list multiple trusted IPs separated by a comma.
You can also use the * wildcard (at the end of a definition only) or use the keyword 'all' to represent any ip address.*/
//$config['Misc']['proxyiplist'] = '127.0.0.1, 192.168.*, all';
Also, in 4.2.4 an extra fix was added due to PHP sometimes not passing the custom headers into the $_SERVER array (which stopped the system working).
Cloudflare gave their IP ranges. Should we enter them as they are shown here even with the /## on the end?
01-30-2017, 12:15 AM
@Paul_M
. In some cases issues can arise form using an older config.php file.
Linear Mode
