3 ms·
I'm reminded of this NPM issue: https://github.com/npm/npm/issues/20791 https://github.com/npm/npm/issues/20791
by molf 8y ago
I'm reminded of this NPM issue: https://github.com/npm/npm/issues/20791 https://github.com/npm/npm/issues/20791
- poizan42 8y agoI don't understand how this happened. Why would a client appending the port in the Host: header result in the server giving that reply? Is it a default joke reply if the npm repository server is confused?
- zaarn 8y agoMost likely it was the server being very confused and not understanding that you could put the port in the Host header (very legit thing to do and proxies do it a lot) So it likely treated it like a bad host header.