Page MenuHomePhabricator

HAProxy 3.0 fires http-after-response rules twice on 500s resulting on KC session state
Closed, ResolvedPublic

Description

We've observed HAProxy firing http-after-response rules twice for internal 500 responses, this has some naugthy side-effects like double reporting twice some fields on x-analytics like ja3n

Event Timeline

Vgutierrez updated the task description. (Show Details)

Change #1248537 had a related patch set uploaded (by Vgutierrez; author: Vgutierrez):

[operations/puppet@production] haproxy: Avoid logging ja3n/ja4h/res_ more than once

https://gerrit.wikimedia.org/r/1248537

Change #1248537 merged by Vgutierrez:

[operations/puppet@production] haproxy: Avoid logging ja3n/ja4h/res_ more than once

https://gerrit.wikimedia.org/r/1248537

Change #1248541 had a related patch set uploaded (by Vgutierrez; author: Vgutierrez):

[operations/puppet@production] haproxy: Fix syntax error

https://gerrit.wikimedia.org/r/1248541

Change #1248541 merged by Vgutierrez:

[operations/puppet@production] haproxy: Fix syntax error

https://gerrit.wikimedia.org/r/1248541