- 🇦🇺Australia darvanen Sydney, Australia
I'm in favour of using Drupal's API by default having run into reverse proxy issues in the past.
Bumping this issue for discussion.
If approved, this might be grounds for a change in major version.
When checking for the user's ip, the module should use Drupal's existing ip check ip_address().
We can still allow overriding of the request header, but if that's empty the fallback should be ip_address() which already uses REMOTE_ADDR by default.
Related to closed issue #2291791: Determine client original IP →
Active
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I'm in favour of using Drupal's API by default having run into reverse proxy issues in the past.
Bumping this issue for discussion.
If approved, this might be grounds for a change in major version.