Misleading error when connecting to wrong port

[ericraio]

Issue

I had a misconfiguration where my server was set up to connect to the default port, but I was running Memcache on a different port. When I went to cache data into Memcache, I was triggering the precondition in the ResponseCode. I logged the bytes with the result 18516 to see if it was an unhandled response code and later learned that I had this misconfiguration and that was the issue.

The precondition was a bit misleading and think there's an opportunity for improvement.