{"push_id":782338309,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a8d477f9ad33d7790f94ffc563e2205823e62515","before":"8c653d4a279eba6354815bb1f3273de5498726d9","commits":[{"sha":"a8d477f9ad33d7790f94ffc563e2205823e62515","author":{"email":"1a73af9e7ae00182733b2292511b814be66f065f@taoeffect.com","name":"Greg Slepak"},"message":"0.5.3 - added optional CORS support for clientside JS API access\n\n- __New Features:__\n    + Optional CORS support from [Michael Bumann](https://twitter.com/bumi) (thanks!).\n- __Improvements:__\n    + Bumped `hiredis` to 0.4.1 for latest iojs compat.\n\nAlthough DNSChain isn't intended to be used from JavaScript within the web browser (unless it's via a browser extension), this releases makes that possible. Doing so allows client-side JavaScript to access blockchain data via the RESTful API, and \"secured\" (not really) by X.509 and HTTPS.\n\nTo enable this, add the following to your DNSChain config:\n\n```\n[http]\n\ncors=true\n```\n\nKeep in mind that enabling this on a public web server means that anyone on the Internet can use it to access blockchain data. You may therefore want to test and adjust the request rate limiting settings as necessary.\n\nThanks to Michael Bumann for this addition!","distinct":true,"url":"https://api.github.com/repos/okTurtles/dnschain/commits/a8d477f9ad33d7790f94ffc563e2205823e62515"}]}