Michael Terry b8ecfed67d fix: use safer ip-chain logic when checking ip for embargos ...

Specifically:
- check ALL ip addresses in the client ip chain for blocking
- check RIGHTMOST ip address in the client ip chain for allowing

Before, we always checked the LEFTMOST ip address in both cases.

AA-1234

2022-04-22 11:15:02 -04:00

..

fixtures

refactor: Ran pyupgrade on openedx/core/djangoapps/embargo (#26911)

2021-03-18 18:38:09 +05:00

migrations

refactor: Ran pyupgrade on openedx/core/djangoapps/embargo (#26911)

2021-03-18 18:38:09 +05:00

tests

fix: use safer ip-chain logic when checking ip for embargos

2022-04-22 11:15:02 -04:00

__init__.py

Move embargo from common to openedx/core/djangoapps.

2016-11-07 08:47:36 -05:00

admin.py

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

api.py

fix: use safer ip-chain logic when checking ip for embargos

2022-04-22 11:15:02 -04:00

exceptions.py

refactor: Ran pyupgrade on openedx/core/djangoapps/embargo (#26911)

2021-03-18 18:38:09 +05:00

forms.py

feat: New codemods on OpenedX 2 (#28777)

2021-10-28 16:45:53 +05:00

messages.py

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

middleware.py

fix: use safer ip-chain logic when checking ip for embargos

2022-04-22 11:15:02 -04:00

models.py

fix: use safer ip-chain logic when checking ip for embargos

2022-04-22 11:15:02 -04:00

test_utils.py

refactor: Ran pyupgrade on openedx/core/djangoapps/embargo (#26911)

2021-03-18 18:38:09 +05:00

urls.py

fix: fixed django4 warnings (#29643)

2022-03-04 15:03:02 +05:00

views.py

fix: use safer ip-chain logic when checking ip for embargos

2022-04-22 11:15:02 -04:00