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
Is your feature request related to a problem? Please describe.
Sometimes you need to get screenshots of vhosts on a particular IP. But chrome will just do a DNS resolve of the provided hostname, and pick an address in the response to connect to. This may not always be the IP address that you are interested in!
Describe the solution you'd like
It would be great to be able to specify the IP address that chrome should connect to, for the various URL's provided.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This can be worked around by creating entries in /etc/hosts to return only the IP address that you want for each hostname, but that gets a little bit complicated when running in a Docker container. Since there is a reasonable workaround, this is obviously a low priority suggestion.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sometimes you need to get screenshots of vhosts on a particular IP. But chrome will just do a DNS resolve of the provided hostname, and pick an address in the response to connect to. This may not always be the IP address that you are interested in!
Describe the solution you'd like
It would be great to be able to specify the IP address that chrome should connect to, for the various URL's provided.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This can be worked around by creating entries in /etc/hosts to return only the IP address that you want for each hostname, but that gets a little bit complicated when running in a Docker container. Since there is a reasonable workaround, this is obviously a low priority suggestion.
The text was updated successfully, but these errors were encountered: