Use hostname instead of host when creating request

[cjlpowers]

Description

It is common to host services on different ports during development / testing. I noticed a DNS failure when the jwks endpoint was served with a port. For example http://localhost:3000/oidc/jwks.

The fix is to use hostname instead of host when constructing the request.
You can see the difference between host and hostname in the scenarios below.

urlUtil.parse('http://localhost:3000/oidc/jwks')
{
  protocol: "http:",
  slashes: true,
  auth: null,
  host: "localhost:3000",
  port: "3000",
  hostname: "localhost",
  hash: null,
  search: null,
  query: null,
  pathname: "/oidc/jwks",
  path: "/oidc/jwks",
  href: "http://localhost:3000/oidc/jwks",
}

urlUtil.parse('http://localhost/oidc/jwks')
{
  protocol: "http:",
  slashes: true,
  auth: null,
  host: "localhost",
  port: null,
  hostname: "localhost",
  hash: null,
  search: null,
  query: null,
  pathname: "/oidc/jwks",
  path: "/oidc/jwks",
  href: "http://localhost/oidc/jwks",
}

urlUtil.parse('http://127.0.0.1:3000/oidc/jwks')
{
  protocol: "http:",
  slashes: true,
  auth: null,
  host: "127.0.0.1:3000",
  port: "3000",
  hostname: "127.0.0.1",
  hash: null,
  search: null,
  query: null,
  pathname: "/oidc/jwks",
  path: "/oidc/jwks",
  href: "http://127.0.0.1:3000/oidc/jwks",
}

Testing

Call jwksRsa.passportJwtSecret using a jwksUri containing a port (e.g. http://localhost:3000). Notice the ENOTFOUND failure caused by dns resolution errors.

Checklist

• I have added documentation for new/changed functionality in this PR or in auth0.com/docs
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not master

[MelvinVermeer]

Any updates on this PR?

Having this PR merged and released would allow us me to migrate to jwks-rsa v2 in my software.

[cabelitos]

I can confirm that this is also affecting us.

[djejaquino]

Thanks for this @cjlpowers and @davidpatrick
Any ETA on the release?