Doug Keen

I looked into this a bit, and it seems related to the[ not-so-great uptime of search.maven.org](https://status.maven.org/): This will cause failures when: 1. [Defaulting to using latest openapi-generator version](https://github.com/OpenAPITools/openapi-generator-cli/blob/66b78fff0b24d0a91d90786d3b6f7937ee274cf6/apps/generator-cli/src/app/app.module.ts#L41), since that...

For contrast, here's the uptime of the CDN from where the openapi-generator jars are actually downloaded: It would be great if there was a way to specify the exact openapi-generator...

I did some research on this issue today, and it looks like it only affects Node v16 and lower. In Node 16, `useNativeURL == true`, and in higher versions, `useNativeURL...

Yup, just confirmed that the `http` protocol (and `https`) that this library wraps only looks at the `auth` field on the `options` object to compute an Authorization header, and disregards...

> It assigns it to the second parameter: > > https://github.com/follow-redirects/follow-redirects/blob/35a517c5861d79dc8bff7db8626013d20b711b06/index.js#L585 > Oh tricky, didn't see the sneaky mutation via object ref. I can take a crack at a PR...