Skip to content

new URL bug with Ada in 18.x #48117

Description

@7c

Version

18.16.0

Platform

Linux xxx.com 5.19.0-1025-aws #26~22.04.1-Ubuntu SMP Mon Apr 24 01:58:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

ubuntu22.04

What steps will reproduce the bug?

Node 18.16.0:

(new URL(`https://${"ZaaZaaaZaaaZbbbZbbbbZ".toUpperCase()}.test.com:443`)).hostname

results to ZaaZaaaZaaaZbbbZbbbbZ.test.com

Node <=18.13.0 results to zaazaaazaaazbbbzbbbbz.test.com.

Since lowercasing is part of IDNA (regarding ada-url/ada#129 (comment)) and all browsers also seem to lowercase everything, this is a bug, because only "Z" is kept uppercase in my tests. This bug caused big problems in our application, this is how we have detected this problem.

How often does it reproduce? Is there a required condition?

in new ADA parser >=18.16.0

What is the expected behavior? Why is that the expected behavior?

see the report

What do you see instead?

see the report

Additional information

No response

Activity

  1. KhafraDev commented on May 22, 2023

    @KhafraDev
    Member

    Fixed in #47598

  2. anonrig commented on May 22, 2023

    @anonrig
    Member

    This issue is already fixed:

    Welcome to Node.js v20.2.0.
    Type ".help" for more information.
    > (new URL(`https://${"ZaaZaaaZaaaZbbbZbbbbZ".toUpperCase()}.test.com:443`)).hostname
    'zaazaaazaaazbbbzbbbbz.test.com'
    
  3. added
    whatwg-urlIssues and PRs related to the WHATWG URL implementation.
    on May 22, 2023
  4. anonrig commented on May 22, 2023

    @anonrig
    Member

    @nodejs/releasers Can we backport & include Ada v2.x changes in the next 18 release?

  5. RafaelGSS commented on May 22, 2023

    @RafaelGSS
    Member

    Do we have an open PR backport? If that lands cleanly on v18.x it will be included.

  6. reopened this on May 22, 2023
  7. changed the title [-]new URL bug with Ada[/-] [+]new URL bug with Ada in 18.x[/+] on May 22, 2023
  8. Trott commented on May 22, 2023

    @Trott
    Member

    Re-opening because the bug is in 18.x and that's a supported release. Feel free to close if you feel strongly it should be closed. I'd prefer to wait until the bug-fix lands in the v18.x branch, if not a release, but I don't feel so strongly about it that I'll argue to keep this open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    whatwg-urlIssues and PRs related to the WHATWG URL implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions