check for nil response. update Readme

[mmoyle]

Fix for ⠋panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x157bc74]

when an http proxy is set. Or for whatever reason a response is not returned by the http client.

Update README.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[bitte-ein-bit]

Hey @mmoyle Thanks for catching and fixing this one. Can you accept the CLA so I can merge this? Thank you!

Also the more go idiomatic approach would be to return an error if the response is nil.

[mmoyle]

Hi @bitte-ein-bit , thanks for the quick reply.

I did agree to the CLA. And force pushed two times. Not sure why it's pending.

For my issue the error is returned on line 129.

This is consistent with the documentation for net/http "If the returned error is nil, the Response will contain a non-nil Body which the user is expected to close." https://pkg.go.dev/net/http#Client.Do

[coveralls]

Pull Request Test Coverage Report for Build 8061893863

Details

• 0 of 11 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 28.719%

---

Totals
Change from base Build 8054055802:	0.2%
Covered Lines:	417
Relevant Lines:	1452

---

💛 - Coveralls

[bitte-ein-bit]

@mmoyle I've checked the CLA backend and can confirm the signature.