4 ms·
I'd leave the "bug" in too... much in the same way every web-protocol software since forever has kept the misspelling of 'referer' intact. Breaking the commonl
by georgemcbay 15y ago
I'd leave the "bug" in too... much in the same way every web-protocol software since forever has kept the misspelling of 'referer' intact.
Breaking the commonly used standard isn't a good idea. As long as the behavior is documented and consistent, don't modify it for pedantic reasons, particularly when the modification will break existing code and cause confusion for people who expect the other behavior due to it working that way in browsers.
- jbri 15y agoThe difference I guess is that rather than "referer" having only one setup (the way it's specced and the way it's implemented are identical), in this case there are two competing methods: The way browsers do it, and the way every other language library does it (which is, incidentally, the way the spec says it should be done).
- georgemcbay 15y agoYeah my analogy certainly isn't a perfect one and that is a good point, but for node.js I'd still argue that being compatible with JavaScript running on browsers (even if that means being 'wrong') is much more important than being compatible with other languages.