It appears this is caused by the patch for CVE-2016-6816 which tightened the validation rules for invalid characters. Unfortunately, it appears the pipe character was commonly used even though it is contrary to RFCs.
There is a bug upstream about the issue, which I've linked to this bug:
Ideally, your application should be modified to not use the invalid character, or if that isn't possible, downgrading the package could be a workaround until we see if upstream makes the more strict validation optional or not.
Hi, thanks for reporting this issue.
It appears this is caused by the patch for CVE-2016-6816 which tightened the validation rules for invalid characters. Unfortunately, it appears the pipe character was commonly used even though it is contrary to RFCs.
There is a bug upstream about the issue, which I've linked to this bug:
https:/ /bz.apache. org/bugzilla/ show_bug. cgi?id= 60594
Ideally, your application should be modified to not use the invalid character, or if that isn't possible, downgrading the package could be a workaround until we see if upstream makes the more strict validation optional or not.