Handle empty ports with new URL parsing#13832
Conversation
|
Thanks, you beat me to the fix! One thing to consider with this is that new lock files will be slightly different. Old parsing didn't drop the empty port:
But new logic drops the colon:
The new behavior is compliant with the RFC (https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.3):
But I'm pretty sure that the canonicalization shim here effectively solves this issue and newer nix versions will not consider the lock file outdated (note the Lines 290 to 300 in 1e16a54 |
|
Interesting, yes we can confirm that if I do a lock with this PR and then run |
Even if they did, it is easy to just remove the |
…3832 Handle empty ports with new URL parsing (backport #13832)
Motivation
Fix #13830
Context
@sbc64 mentioned he had an issue with the new URL handling and it looked simple to fix, so I took the liberty of doing so.
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.