AWS will send a request to a specific path and make sure it receives a
status 200 response. If the response status is not 200, it will consider
that instance unhealthy and will not route traffic to that instance. The
path can be anything that can be used as a signal that the application is
running
We would find this valuable for the reason Jonas outlined. Health checks
from AWS are sent without a host header, which causes the request to fail
the host check. By whitelisting the health check path, it would simplify
deployments to AWS and possibly others. Here's the workaround we use in
product
Sorry all, disregard my previous email, I misread one thing and
completely missed Wim's original message.
On Thu, Mar 8, 2012 at 11:07 PM, Matt Pegler wrote:
> For the project I am working on, we solved this by making a custom
> auth backend that checks the username against the e
For the project I am working on, we solved this by making a custom
auth backend that checks the username against the email column. We've
found it to be a nice clean solution to wanting to use email addresses
instead of usernames.
On Thu, Mar 8, 2012 at 9:54 PM, Clay McClure wrote:
> "Django is a
