fix(hawk): never use RemoteAddr for host/port

I encountered a problem where the MAC was failing because the server was
using the RemoteAddr port in the normalized string and the client was
using the servers.

I don't understand when using RemoteAddr would ever make sense here.
Merge pull request #1 from philips/master

fix(hawk): never use RemoteAddr for host/port