Empty Referrer Policy
1 Intentional IssuesThe referrer meta tag is declared with an empty content attribute. A presence check would call this configured; the extractor must not.
Expected result: referrer_policy_header (#70) DETECTED
And meta_name_referrer (#22) not detected — it is isActive: false and the crawler carries a comment where the check used to be, so no fixture can produce it. #70 is the code that owns referrer policy now, and it reads the meta tag as well as the HTTP header.
What is declared
<meta name="referrer" content="">The extractor reads .attr("content")?.trim() || null, so an empty value and an absent tag produce the same null. An empty policy is not a policy, and the check treating the two alike is the behaviour this page pins down.
The pair
This page is only half a test. /invalid-meta-referrer-token declares a value that is non-empty and not a real Referrer Policy token, and the check stays silent on it. Together the two say where the boundary is. /fp-meta-referrer is the valid control. Index: /malformed-fixtures.