fix: correct RFC reference in comments

RFC 9110 obsoletes RFC 7230 and has more relaxed rules. The strict
validation follows RFC 7230 rules, not RFC 9110.

Author: RajeshKumar11

lib/_http_common.js

@@ -256,7 +256,7 @@ function checkIsHttpToken(val) {
   return true;
 }
 
-// Strict header value regex per RFC 7230/9110:
+// Strict header value regex per RFC 7230:
 // field-value = *( field-content / obs-fold )
 // field-content = field-vchar [ 1*( SP / HTAB ) field-vchar ]
 // field-vchar = VCHAR / obs-text
@@ -272,7 +272,7 @@ const lenientHeaderCharRegex = /[\x00\x0a\x0d]|[^\x00-\xff]/;
 
 /**
  * True if val contains an invalid header value character.
- * By default uses strict validation per RFC 7230/9110.
+ * By default uses strict validation per RFC 7230.
  * When lenient=true, uses relaxed validation per Fetch spec.
  * @param {string} val
  * @param {boolean} [lenient=false] - Use lenient validation (Fetch spec rules)

test/parallel/test-http-invalidheaderfield2.js

@@ -60,7 +60,7 @@ const { _checkIsHttpToken, _checkInvalidHeaderChar } = require('_http_common');
 
 
 // ============================================================================
-// Strict header value validation (default) - per RFC 7230/9110
+// Strict header value validation (default) - per RFC 7230
 // Rejects control characters (0x00-0x1f except HTAB) and DEL (0x7f)
 // ============================================================================