A library application behaves differently when the same parameter name appears twice in a request and authorization checks flip unexpectedly. What technique class is the tester observing?
Select an answer to reveal the explanation.
Short Explanation
When two clerks read the same form field differently, chaos follows. Duplicate parameters that change which value the app trusts are HTTP parameter pollution — parsers disagree, and authz can slip. That is not BGP drama or a Kerberos cipher debate.
Full Explanation
HTTP parameter pollution occurs when duplicate parameter names cause inconsistent parsing between layers (proxies, frameworks, application code), potentially altering authorization or validation outcomes. Testers should treat unexpected dual-parameter behavior as an HPP awareness finding and map which value each layer consumes. Unrelated networking or Kerberos issues do not explain this class. Remediation centers on strict parameter handling and consistent server-side parsing.