Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way to forcibly connect to IPv4 or IPv6 ? #3196

Open
sweepkim opened this issue Feb 1, 2024 · 0 comments
Open

Is there a way to forcibly connect to IPv4 or IPv6 ? #3196

sweepkim opened this issue Feb 1, 2024 · 0 comments

Comments

@sweepkim
Copy link

sweepkim commented Feb 1, 2024

  1. Newman Version (can be found via newman -v): 6.1.0
  2. OS details (type, version, and architecture): Ubuntu 18.04 64bit
  3. Are you using Newman as a library, or via the CLI?: Library
  4. Did you encounter this recently, or has this bug always been there: Recently Required
  5. Expected behaviour: Hope to set ip type version for each request.
  6. Command / script used to run Newman: newman.run
  7. Sample collection, and auxiliary files (minus the sensitive details): Not required
  8. Screenshots (if applicable):

As far as I know, If the OS supports Dual Stack(IPv4 and IPv6), the newman supports both IPv4 and IPv6 connection.
However, Is there a way to forcibly connect to IPv4 or IPv6 when sending a request ?
For example, If the target server supports IPv4, It is necessary to forcibly connect IPv6 to see if the settings for additional IPv6 support are correct.
If it's connected to IPv4, It will be difficult to check the IPv6 connection status.

If I can set host or family in newman library, It's helpful to define IP type.
https://nodejs.org/api/http.html#agentgetnameoptions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant