httl cli seems to malfunction in node18

[PeterGrace]

test file

  $   cat test.httl
@base: http://localhost:3003/api/v1

Authorization: ApiKey 641bbc8eed048b3aab6a51bed3eb8b37

#post /workflows {
#    name: "my workflow"
#}
post /actions {
    name: "my workflow"
}

node 18

 $   nvm use v18.20.4
Now using node v18.20.4 (npm v10.7.0)

 $   npm install httl-cli -g

changed 19 packages in 249ms

17 packages are looking for funding
  run `npm fund` for details

 $   httl test.httl
⢎   Loading...[
  {
    "error": "connect ECONNREFUSED ::1:3003",
    "token": {
      "start": 140,
      "end": 181,
      "text": "post /actions{name:\"my workflow\"}"
    },
    "severity": 1
  }
]

node 20

  $   nvm use lts/iron
Now using node v20.18.3 (npm v10.8.2)

  $   npm install httl-cli -g

changed 19 packages in 215ms

17 packages are looking for funding
  run `npm fund` for details

  $   httl test.httl
 HTTP/1.1 200 OK
access-control-allow-origin: *
content-length: 14
content-type: text/plain; charset=utf-8
date: Fri, 21 Feb 2025 01:07:32 GMT
set-cookie: id=YUVoekqyOCSdGL3VlM2DtA; HttpOnly; SameSite=Strict; Path=/; Max-Age=86400
vary: origin, access-control-request-method, access-control-request-headers

Action created

[lojell]

Thanks @PeterGrace, looking on it

[lojell]

@PeterGrace, strange thing, but I can't reproduce it.
Would you please share the framework behind the URL http://localhost:3003/?
I will try to recreate it locally.

[PeterGrace]

@PeterGrace, strange thing, but I can't reproduce it. Would you please share the framework behind the URL http://localhost:3003/? I will try to recreate it locally.

I just dug into this a bit more on my side and it appears that node18 preferred the ipv6 localhost address, which my app was not bound to:

  $   sudo netstat -anlp | grep 3003
tcp        0      0 0.0.0.0:3003            0.0.0.0:*               LISTEN      468234/target/debug

In the output in node 18 we see:

  {
    "error": "connect ECONNREFUSED **::1:3003",**

where ::1 is the ipv6 equivalent of 127.0.0.1/localhost.

I'm not sure if this is an httl issue after-all, it may just be that node18 preferred ipv6 for some reason where node20 preferred ipv4.

[lojell]

Oh, awesome! Great find. Let me handle this also.

[lojell]

@PeterGrace, turns out we can force the Node.js HTTP client to resolve domains in IPv4 format.

Thanks for catching this issue. Fixed! Please install the latest version.