Comment 4 for bug 1629058
Revision history for this message
| Colin Watson (cjwatson) wrote Re: Can access released packages | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I see - thanks for the detailed explanation. I believe that this is because the colon in the package's version isn't being URL-encoded in that link, so Chrome/Chromium takes a strict interpretation of it as an unknown scheme or similar while Firefox tolerates it. RFC 1738 is clear that we should be URL-encoding the colon.