Philippe Verdy via Unicode
unicode at unicode.org
Wed Oct 4 15:55:20 CDT 2017
continuousbuilds may just check the statue of the short shasums files to
know when one has changed, this would not use lot of bandwidth. Anyway if
your website supports HTTP mime requests for conditional downloads , or if
clients are using HEAD ratrher than GET requests to get metadata, this
saves a lot, without having to download again the same copy of large files.
2017-10-04 22:43 GMT+02:00 Steven R. Loomis via Unicode <unicode at unicode.org
> Also just a public note. please do NOT fetch from unicode.org/Public as
> part of continuous builds (Jenkins, travis, etc). That's too much load for
> files that change *yearly*. Fetch one copy of the data and use your own
> copy until it is time to update.
> Yes, shasums and signatures are great. ICU (now part of Unicode) has been
> doing this for years. I just signed up this morning to provide such for
> CLDR data. So let's see about UCD data also.
> On Wed, Oct 4, 2017 at 2:14 AM, Mathias Bynens via Unicode <
> unicode at unicode.org> wrote:
>> unicode.org and www.unicode.org are now available over HTTPS. E.g.
>> On Thu, Mar 6, 2014 at 3:54 PM, Robbert <mail at robbertbroersma.nl> wrote:
>>> For tools that rely on the Unicode database it would be great if the
>>> databases were available over HTTPS as well:
>>> In addition to this it would be helpful if the archive also contains
>>> SHA512 checksum files for each Unicode version to verify the integrity of
>>> databases that have already been downloaded (over HTTP), e.g.:
>>> Mozilla already offers such checksums, although unfortunately not over
>>> HTTPS, but they can serve as an example.
>>> I think this would improve the security of many libraries that directly
>>> and indirectly depend on Unicode.
>>> Kind regards,
>>> Robbert Broersma
>>> Unicode mailing list
>>> Unicode at unicode.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unicode