You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newman Version (can be found via newman -v): 6.1.0
OS details (type, version, and architecture): Ubuntu 18.04 64bit
Are you using Newman as a library, or via the CLI?: Library
Did you encounter this recently, or has this bug always been there: Recently Required
Expected behaviour: Hope to set ip type version for each request.
Command / script used to run Newman: newman.run
Sample collection, and auxiliary files (minus the sensitive details): Not required
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.
newman -v
): 6.1.0As 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
The text was updated successfully, but these errors were encountered: