Inspect the three failing, skipped unittests with full server blocking
CrsiX opened this issue · comments
0af8a1c added three new unittests which all show similar behavior of blocking the main server after a specific amount of requests in a short period of time (even though waiting of one second between requests didn't prevent the issue). This can be easily exploited to cause DoS through frontend applications and must be resolved.
It looks like the behavior of this three test cases is not reproducible when running the program outside of any unittest. Inside the unittests, however, they do fail (also with very minimal configuration and almost no middlewares attached). This leads to the question if that could be the result of how the program is started inside the unittesting structure.