Applying it on top of we have indeed fixed the issue. But when applying all changes in version 0.12.1, the same test fails again. The problem seems to be this commit:
Not sure if this change is intentional. BTW the link in the commit message here is not accessible without logging in, it would be great if the info is public.
In Debian and Ubuntu, I have experienced some test failures in other ruby gems like this one:
This is a simple test:
After some digging, I noticed that this issue would be fixed by this commit:
https://github.com/ruby/uri/commit/ffbab83de6d8748c9454414e02db5317609166eb
Applying it on top of we have indeed fixed the issue. But when applying all changes in version 0.12.1, the same test fails again. The problem seems to be this commit:
https://github.com/ruby/uri/commit/eaf89cc31619d49e67c64d0b58ea9dc38892d175
Since the regex is not easy to read I was not able yet to pinpoint the issue introduced by this change, sorry.
This is a straightforward reproducer for the behavior change:
1- Without the security fix:
2 - With the security fix in 0.12.1 applied:
Not sure if this change is intentional. BTW the link in the commit message here is not accessible without logging in, it would be great if the info is public.