accept 200 as range read response, add context option

The changes included here

• Accept a 200 OK response status when requesting a range. It seems some servers will respond with 200 OK, instead of 206 Partial Content, when the range hits the end of the content length.
• Allow passing in a context via an option.

Fix hashing error checking

What's Changed

• Return error when there is/are error(s) by @dbyington in #11

Full Changelog: v1.1.7...v1.1.8

Minor fix to hasher

This prevents leaving a valid http response body open when returning from hashing a url.

What's Changed

• Defer http response body before doing anything else by @dbyington in #10

Full Changelog: v1.1.6...v1.1.7

Fix hashing final chunk when less than chunk size

This patch release fixes an issue where the hash would be incorrect for the final chunk of the content. This would happen in cases where the chunk size was smaller than the content length and would not split the content evenly, meaning the final chunk size would be less than the chunk size.

Conform to the rules

Merge pull request #7 from dbyington/fix_method_implementation

Fix the HTTPStatus return values

Add a small method for getting request error detail

Merge pull request #6 from dbyington/httpstatus_func

add method HTTPStatus to request error

Empty, for sum.golang caching

Merge pull request #5 from dbyington/check_head_status_code

check the response code from head to assert status

Set status code in error after head of url

Merge pull request #5 from dbyington/check_head_status_code

check the response code from head to assert status

Include helpers to get configured values

Merge pull request #4 from dbyington/add-helpers

Add helpers

hash content in chunks concurrently

This release goes back to the original method of how HashURL is called, the hash chunk size is now an Option.