Closed (fixed)
Project:
Droptor
Version:
7.x-2.71
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Jul 2011 at 20:30 UTC
Updated:
28 Sep 2011 at 23:29 UTC
droptor_check_domain() always fails on websites which are running behind a reverse proxy, as $_SERVER['REMOTE_ADDR'] is the IP of the proxy, not the IP of the real client.
It seems like Drupal core already has a function ip_address() which looks for the X-Forwarded-For HTTP header if the site is known to run behind a reverse proxy.
Comments
Comment #1
cyberwolf commentedSorry for initially reporting the wrong version number.
I see in git now this was fixed in January already (commit 03280a50a22f0785e26f60b4d918e7ce9e2fb820). Any chance to get this in the 2.x branch as well? Or should I go for 3.x-dev?
Comment #2
jemond commentedHey Cyberwolf. You should go right to 3.0, it should be stable.
Comment #3
cyberwolf commentedBut there is no stable release out yet for the 3.x branch? I only see 3.x-dev.
Comment #4
jemond commentedHey Cyberwolf,
I will be releasing 3.0 very soon. It will have this fix.
Cheers,
jpe
Comment #5
jemond commentedComment #6
zilverdistel commentedsubscribing
Comment #7
jemond commentedThis is fixed! The release will appear when the d.o crawler does the update... 7.x-2.8