There appears to be a bug in the HTML meta tag validation logic. The log message about an unacceptable referrer policy is triggered when the outcome is SpecificationFullyImplemented.
|
if (Result.Outcome == TestOutcomes.SpecificationFullyImplemented) { |
|
LogInfo("A referrer policy was specified as an HTML meta tag, but it was not acceptable.", "one of: " + string.Join(", ", safeMetas), value); |
|
} |
This seems inconsistent with the similar check for HTTP headers on line 56, which uses SpecificationNotImplemented.
There appears to be a bug in the HTML meta tag validation logic. The log message about an unacceptable referrer policy is triggered when the outcome is
SpecificationFullyImplemented.OAuch/src/OAuch/OAuch.Tests/Tests/AuthEndpoint/ReferrerPolicyEnforcedTest.cs
Lines 77 to 79 in 40a517c
This seems inconsistent with the similar check for HTTP headers on line 56, which uses
SpecificationNotImplemented.