{"action":"closed","issue":{"url":"https://api.github.com/repos/django-debug-toolbar/django-debug-toolbar/issues/690","labels_url":"https://api.github.com/repos/django-debug-toolbar/django-debug-toolbar/issues/690/labels{/name}","comments_url":"https://api.github.com/repos/django-debug-toolbar/django-debug-toolbar/issues/690/comments","events_url":"https://api.github.com/repos/django-debug-toolbar/django-debug-toolbar/issues/690/events","html_url":"https://github.com/django-debug-toolbar/django-debug-toolbar/issues/690","id":58735583,"number":690,"title":"Could you change the way to examine the INTERNAL_IPS?","user":{"login":"haudoing","id":1922489,"avatar_url":"https://avatars.githubusercontent.com/u/1922489?v=3","gravatar_id":"","url":"https://api.github.com/users/haudoing","html_url":"https://github.com/haudoing","followers_url":"https://api.github.com/users/haudoing/followers","following_url":"https://api.github.com/users/haudoing/following{/other_user}","gists_url":"https://api.github.com/users/haudoing/gists{/gist_id}","starred_url":"https://api.github.com/users/haudoing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haudoing/subscriptions","organizations_url":"https://api.github.com/users/haudoing/orgs","repos_url":"https://api.github.com/users/haudoing/repos","events_url":"https://api.github.com/users/haudoing/events{/privacy}","received_events_url":"https://api.github.com/users/haudoing/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-02-24T13:07:31Z","updated_at":"2015-02-24T15:01:51Z","closed_at":"2015-02-24T15:01:51Z","body":"Currently it's using REMOTE_ADDR for checking INTERNAL_IPS, but I think it might not be a proper way. Because gunicorn doesn't provide REMOTE_ADDR when using the unix socket. related post [here](https://github.com/benoitc/gunicorn/issues/797). I think the better way is checking \"X-Forwarded-For\" for now."}}