3 ms·
Just been fixed, apparently[0]: > We've fixed this -- we now accept the port appended to the host. @wgrant's comment was most helpful, thank you! [0] https://
by stevenjohns 8y ago
Just been fixed, apparently[0]:
> We've fixed this -- we now accept the port appended to the host. @wgrant's comment was most helpful, thank you!
[0] https://github.com/npm/npm/issues/20791#issuecomment-392648459 https://github.com/npm/npm/issues/20791#issuecomment-3926484...
- nneonneo 8y agoThey did fix it, but e.g. appending a period (https://registry.npmjs.org./ https://registry.npmjs.org./) still throws a 418 - I expect this to bite them someday (eventually). I don't understand why their Host: parsing is so strict; it seems unnecessarily restrictive.
- gpvos 8y ago418 is really a confusing response here. They should fix that ASAP by giving a normal error message.
- nneonneo 8y agoI would recommend (if any NPM people are reading this) that the error for an unknown Host header be changed to 404. Bad host headers are already filtered out by Cloudflare (which returns 400), so any host headers that make it through would represent "unknown"/"missing" hosts (hence 404).
- ulkesh 8y agoWith no explanation about it being a 418. Par for the course, I suppose.