On Wed, Jul 26, 2017 at 11:38:47AM -0700, Kevin McArthur wrote: > > However I have a good news. I found that it was possible to access the > > connection from the verify callback! With a connection comes the ability > > to place a specific error code which we can verify later. So I did this, > > 1) add a new error code for a wrong certificate, and 2) add the check for > > this specific use case (ie: cert name verification failed against a non- > > hardcoded value, so fail immediately). It now immediately reports the > > 503 and you don't have the retries anymore. > > This patch is working flawlessly. > > +1 to adding all three patches to master.
Thanks for testing. Let's sleep over this series to see if we can do something better for the checks before merging all of this. Willy
