HTTP HMAC Signer for Go

An implementation of the HTTP HMAC Spec in Golang.

Run tests

To run the test cases use the make command make test

Run code coverage

To get the code coverage use the make command make coverage

http-hmac-go's People

Contributors

Stargazers

Watchers

http-hmac-go's Issues

Reduce verbosity in search.go

Lots of debug stuff logging.

2016/06/01 19:07:03 search.go:116: acquia_solr_time: 1464822423
2016/06/01 19:07:03 search.go:116: acquia_solr_nonce: ABCDEFGHIJKLMNOPQRSTUVWX
2016/06/01 19:07:03 search.go:116: acquia_solr_hmac: b0f2fac31d1324d44b9927357d2881197165db9f
/solr/DEVY-83854.prod.volpe/admin/ping?41fe27db16274556339a06d80bdf217eba0ebaad2016/06/01 19:07:03 search.go:168: Path and Query: /solr/DEVY-83854.prod.volpe/admin/ping?S: 41fe27db16274556339a06d80bdf217eba0ebaad
2016/06/01 19:07:03 http: proxy error: dial tcp: lookup tcp/: nodename nor servname provided, or not known
2016/06/01 19:07:03 search.go:116: acquia_solr_time: 1464822423
2016/06/01 19:07:03 search.go:116: acquia_solr_nonce: ABCDEFGHIJKLMNOPQRSTUVWX
2016/06/01 19:07:03 search.go:116: acquia_solr_hmac: b0f2fac31d1324d44b9927357d2881197165db9f

Do not add the X-Forwarded-Port if this wasn't present in the signature, eg port 443 and port 80

We are in a limbo state when the request went to https://domain and the library receives the X-Forwarded-Port for port 443. It will add https://domain:443 to the signature and the signatures will not match. Only in cases where the port was explicitly added we should add it to the signature. I dont know how we can check this yet. My suggestion perhaps is to accept both hashes or think really hard if there is no other way we can identify this.