Thanks to @hazbot sharing some flows and info privately, I have confirmed the issue.
It is fixed in master
and will be part of a maintenance release soon.
However, in the mean time, for anyone with a similar issue, a simple workaround is to set the user-agent
manually (note the LOWER_CASE user-agent
)
Via UI
Or, via the msg