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
Fortio client aborts because it receives 404 instead of 200: "Aborting because error 404 for http://..." Is it possible to keep sending requests, despite the received error code and do not abort?
Thank you very much,
Apostolos
The text was updated successfully, but these errors were encountered:
404 means not found, is that really what you want to test? you can use -n mode to skip the warm up but fortio's behavior is to make a new connection (as opposed to normal keep alive) when it gets an http error back, so if you're continuously going to get 404 you're going to make a lot of new connections (which is slow)
Hello,
Fortio client aborts because it receives 404 instead of 200: "Aborting because error 404 for http://..." Is it possible to keep sending requests, despite the received error code and do not abort?
Thank you very much,
Apostolos
The text was updated successfully, but these errors were encountered: