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
Attacking a WCF web service with attacks like Element Count, Hash Collision or XML Overlong Names results in a not successful attack and the log entry:
WARN [PossibleState] Service seems to be down! No request was send successfully. Abort execution.
This error message implies that there was a problem with the service´s availability although the service was available all the time and answered the requests with a HTTP status code "413 Request Entity Too Large".
The plugin should recognize the HTTP code in the answer and therefore stop the attack and give a 0% rating. The error message is not needed/not correct and might confuse the user.
Attacking a WCF web service with attacks like Element Count, Hash Collision or XML Overlong Names results in a not successful attack and the log entry:
This error message implies that there was a problem with the service´s availability although the service was available all the time and answered the requests with a HTTP status code "413 Request Entity Too Large".
The plugin should recognize the HTTP code in the answer and therefore stop the attack and give a 0% rating. The error message is not needed/not correct and might confuse the user.
This can be reproduced using the "WCF-1" sample web service.
The text was updated successfully, but these errors were encountered: