HTTP ERROR 404 when generating client using HTTPS URL

[FredrikErikJohansson]

Description

From v0.61.0 the CLI returns HTTP ERROR 404 when generating the client using a HTTPS URL to a swagger.json

v0.60.1 works as expected

Reproducible example or configuration

openapi-ts -i https://valid-url.com/swagger.json -o src/client -c legacy/fetch

OpenAPI specification (optional)

No response

System information (optional)

No response

[mrlubos]

@FredrikErikJohansson are you able to provide more information or replication steps? I am unable to replicate with the same command in a package.json script

[cpoftea]

@mrlubos same issue here. As you can see I first tested connection manually with response 200, later with openapi-ts with response 400 for the same address (📎 Node log screenshot)

[cpoftea]

v0.60.1 works as expected

I confirm

📎 Node log screenshot 1
📎 Node log screenshot 2

[mrlubos]

Can others here confirm this issue occurs with Node 18? @cpoftea any chance you can switch to Node 20 or 22 to check if the issue persists? It seems like a good starting point, everything else looks similar and you're not even using HTTPS

[cpoftea]

@mrlubos It doesn't look like a Node version problem. But here it is - issue persist.

v20

• v0.61.1
  • 📎 Node log screenshot 1
• v0.60.1
  • 📎 Node log screenshot 1
  • 📎 Node log screenshot 2

v22

• v0.61.1
  • 📎 Node log screenshot 1
• v0.60.1
  • 📎 Node log screenshot 1
  • 📎 Node log screenshot 2

[mrlubos]

@cpoftea Does your URL work when you call it with HEAD method instead of GET? What kind of server is it?

[FredrikErikJohansson]

@mrlubos I tried calling our swagger with HEAD instead of GET and it returns 404

[epfn]

I have same error with 0.61.1 version, API: https://bloshinyj-rynok-api.spaceapp.ru/swagger/v1/swagger.json

Error requesting https://bloshinyj-rynok-api.spaceapp.ru/swagger/v1/swagger.json
HTTP ERROR 404
ResolverError: Error requesting https://bloshinyj-rynok-api.spaceapp.ru/swagger/v1/swagger.json
HTTP ERROR 404
at Object.sendRequest (C:\Users\epfnc\projects\ProTest\node_modules.pnpm@[email protected]\node_modules@hey-api\json-schema-ref-parser\dist\lib\resolvers\url.js:39:15)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async hf (C:\Users\epfnc\projects\ProTest\node_modules.pnpm@[email protected][email protected]\node_modules@hey-api\openapi-ts\dist\index.cjs:1328:7511)
at async n (C:\Users\epfnc\projects\ProTest\node_modules.pnpm@[email protected][email protected]\node_modules@hey-api\openapi-ts\dist\index.cjs:1328:10270)
at async Promise.all (index 0)
at async pA (C:\Users\epfnc\projects\ProTest\node_modules.pnpm@[email protected][email protected]\node_modules@hey-api\openapi-ts\dist\index.cjs:1328:11103)
at async start (C:\Users\epfnc\projects\ProTest\node_modules.pnpm@[email protected][email protected]\node_modules@hey-api\openapi-ts\bin\index.cjs:113:21)

node 22.10.0

[mrlubos]

@epfn thank you for providing the URL, should be way faster to fix

[mrlubos]

Hey all, this will be fixed in the next release and separately I will work on improving the watch mode #1542