[vhffs-dev] [GIT] vhffs4/vhffs.git branch, master, updated. ca05ced8c3304b08f4abd217d88b6c0f93c4d6d0

[git@xxxxxxxxxxxxx]

This is an automated email from git. It was enerated because a ref
change was pushed to the repository "vhffs4/vhffs.git".

The branch, master has been updated
       via  ca05ced8c3304b08f4abd217d88b6c0f93c4d6d0 (commit)
      from  63137b3555339eca622c5dfabc98e02d4f17ec44 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ca05ced8c3304b08f4abd217d88b6c0f93c4d6d0
Author: Sylvain Rochet <gradator@xxxxxxxxxxxx>
Date:   Mon Feb 22 21:56:28 2016 +0000

    tls: try with the staging Let's Encrypt API first
    
    First, try with the Let's Encrypt staging API, that's not really nice
    for Let's Encrypt API servers but their rate limiting is very harsh,
    and we couldn't find a way to prevent behing blacklisted, especially
    the limit about the max failed requests/week (300 failed requests/week
    at the time of writing).
    
    The staging API is not rate limited but deliver certificates that are
    not working, but it tells us whether the validation will succeed
    using the real API :-)

-----------------------------------------------------------------------

Summary of changes:
 vhffs-api/src/Vhffs/Robots/Tls.pm |   30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)


hooks/post-receive
--
vhffs4/vhffs.git