We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried putting entry in /etc/hosts for the site but , the request were going to original site . I will explain with an example:
server_name
abc.efg.ijk.lmn
/etc/hosts
abc.efg.ijk.lmn google.com
abc.txt
htdocs
I have task in my locust taskset that is programmed to hit google.com/abc.txt
task
locust taskset
google.com/abc.txt
but when i run locust --host=http://google.com
locust --host=http://google.com
but request is going to THE google.com
google.com
any help would be greatly appreciated
The text was updated successfully, but these errors were encountered:
Locust uses gevent internally, and I know gevent has been having issues with DNS previously (pre 1.0): http://www.gevent.org/whatsnew_1_0.html#new-dns-resolver
These should have been fixed with gevent 1.0, but you can try setting the environment variable:
GEVENT_RESOLVER=ares
and see if that helps.
You could also try making request with/without gevent from the python REPL to see if there is any issues there, or if it is related strictly to locust
Sorry, something went wrong.
No branches or pull requests
I tried putting entry in /etc/hosts for the site but , the request were going to original site . I will explain with an example:
server_name
directive in vhost's nginx configuration) hosted on a vps with IPabc.efg.ijk.lmn
/etc/hosts
I have put an entryabc.efg.ijk.lmn google.com
.abc.txt
file inhtdocs
of my site google.com, and I am able to access it using google.com/abc.txt .I have
task
in mylocust taskset
that is programmed to hitgoogle.com/abc.txt
but when i run
locust --host=http://google.com
but request is going to THE
google.com
any help would be greatly appreciated
The text was updated successfully, but these errors were encountered: