You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux [redacted] 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
In node do the following
newURL(`https://abc.xyz`).href
How often does it reproduce? Is there a required condition?
N/A
What is the expected behavior?
'https://abc.com'
What do you see instead?
'https://abc.com/'
Additional information
I'm assuming the the URL module in Node is meant to be interoperable with the DOM W3C URL specification. Since doing this command in a browser doesn't produce a trailing slash, it appears to be a bug for Node to add one.
The text was updated successfully, but these errors were encountered:
Hmm it appears that the Location.href in the browser returns it without the trailing slash. So I was mistaken thinking Location is synonymous with URL. Closing.
Version
v16.15.1
Platform
Linux [redacted] 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
In node do the following
How often does it reproduce? Is there a required condition?
N/A
What is the expected behavior?
What do you see instead?
Additional information
I'm assuming the the
URL
module in Node is meant to be interoperable with the DOM W3C URL specification. Since doing this command in a browser doesn't produce a trailing slash, it appears to be a bug for Node to add one.The text was updated successfully, but these errors were encountered: