Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix remote_addr for audits #2

Merged
merged 1 commit into from
Jan 4, 2017
Merged

Fix remote_addr for audits #2

merged 1 commit into from
Jan 4, 2017

Conversation

frankjwu
Copy link

Description

Our audit tables use the flask plugin to automatically track
request remote_addr, the IP address where the change is being
made. The X-Forwarded-For request header gives us the client IP,
not the IP of the Aptible load balancer.

Related JIRA Issues

SPARK-274

Related Pull Requests

Migrations

Extra Deployment Steps

Testing Steps

  • check audit log remote_addr

Description
-----------
Our audit tables use the flask plugin to automatically track
request `remote_addr`, the IP address where the change is being
made. The X-Forwarded-For request header gives us the client IP,
not the IP of the Aptible load balancer.

Related JIRA Issues
-------------------
SPARK-274

Related Pull Requests
---------------------

Migrations
----------

Extra Deployment Steps
----------------------

Testing Steps
-------------
* check audit log remote_addr
@frankjwu frankjwu merged commit fff43ba into master Jan 4, 2017
@frankjwu frankjwu deleted the frank__fix-ip branch May 15, 2017 17:03
EricBorczuk pushed a commit that referenced this pull request Oct 15, 2019
Hotfix/track cloned connections (#2)

Hotfix/track cloned connections (#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections

Hotfix/track cloned connections (#2)

Hotfix/track cloned connections (#3)

change iterations

use only ConnectionFairy as indexes

create new dict entry for clones

create entry using old connection

create entry using session

revert to event listening strategy

remove cloned connections on rollback

treat None case when cleaning connections
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants