Closed AllisonBC closed 3 years ago
I am experiencing a bug in testing this feature-- the properties of users being created by the other running injection tests appear to interfere with this test, somehow.
During testing I receive as output an email generated from a different injection test. When navigating to the webpage I have noticed a lag period where the details of a query via userId are all off by one, then self-corrects after an additional GET request with the same userId.
I spoke with Farhad and learned that there's an error (which Erica is already working on) involving how the Redis cache is implemented in the users/userId function GET method. Until that's fixed, this feature/action will continue to fail as I'm unable to check the results of this injection attempt.
The effect of this error can also be seen in Farhad's feature PR215 in the 10th line of the sample run, the userId retrieved is 1100, not 1101 as referenced in the previous lines above
Closes #200
Creates GitHub action for SQL injection test for HTTP method DELETE to delete /users/{user_id} (from HttpTriggerAPIUsersId api)
What it does:
To test: I tested this task in a fork. (Screenshots to follow)![image](https://user-images.githubusercontent.com/13280802/110198438-51f7d780-7e07-11eb-886a-d87e56294468.png)