Skip to content
Snippets Groups Projects
  1. Jan 16, 2019
  2. Jan 09, 2019
  3. Jan 07, 2019
  4. Jan 04, 2019
  5. Dec 27, 2018
  6. Dec 26, 2018
  7. Dec 21, 2018
  8. Dec 14, 2018
  9. Dec 11, 2018
  10. Dec 04, 2018
  11. Nov 28, 2018
  12. Nov 05, 2018
  13. Oct 31, 2018
  14. Oct 30, 2018
  15. Oct 18, 2018
  16. Oct 17, 2018
  17. Sep 21, 2018
  18. Sep 20, 2018
  19. Sep 13, 2018
  20. Sep 10, 2018
  21. Aug 31, 2018
  22. Aug 24, 2018
  23. Aug 15, 2018
  24. Aug 13, 2018
  25. Aug 10, 2018
  26. Aug 09, 2018
    • Feanil Patel's avatar
      Further downgrade gunicorn. · b90a9c17
      Feanil Patel authored
      18.0 seems to be doing a different thing with REMOTE_ADDR.
      
      Putting this back to the last working version in production.
      b90a9c17
  27. Aug 08, 2018
    • Brian Beggs's avatar
      Set user-util to 0.1.4 · b834daa1
      Brian Beggs authored
      b834daa1
    • Feanil Patel's avatar
      Downgrade `gunicorn` and run `make upgrade` · 056488a9
      Feanil Patel authored
      There is a breaking change in gunicorn 19 which changes
      the behavior of the `REMOTE_ADDR` request meta info. It
      no longer correctly passes through the value of X-Forwarded-For
      if that header is present.
      
      This resulted in making anything that looked at this attribute
      think that all requests were coming from 127.0.0.1
      
      This broke the django-ratelimit-backend library which relies on
      this feature to determine if a user has had too many login attempts.
      056488a9
  28. Aug 07, 2018
  29. Aug 03, 2018
  30. Aug 02, 2018
Loading