今天就学习课程吧!
今天就开通帐号,24,700 门业界名师课程任您挑!
Testing DELETE calls
- [Narrator] Delete calls are pretty self-explanatory. They allow you to delete existing resources from the server. As you can imagine, there are many things you want to carefully test when it comes to deleting things. You don't want to delete the wrong things. We want to make sure that we have all the right checks in place to prevent things from being deleted that should not be. This can take the form of authentication and authorization. In other words, making sure you can't delete other users' content for example. Or making sure that only users with certain permission levels can delete things. It can also take the form of data types. Perhaps only certain things on your server can be deleted. You may have shared resources that you don't want to allow people to delete or you might not allow deleting of an object until its child objects have been removed. Alright, let's take a look at some examples. For this first example…
内容
-
-
-
-
-
-
(已锁定)
Testing GET calls3 分钟 42 秒
-
(已锁定)
Testing PUT calls3 分钟 25 秒
-
(已锁定)
Testing DELETE calls2 分钟 46 秒
-
(已锁定)
Challenge: Break the API1 分钟 43 秒
-
(已锁定)
Solution: Break the API2 分钟 31 秒
-
(已锁定)
Understanding POST calls3 分钟 55 秒
-
(已锁定)
Testing POST calls4 分钟 27 秒
-
(已锁定)
Challenge: Access protected endpoints1 分钟 32 秒
-
(已锁定)
Solution: Access protected endpoints2 分钟 36 秒
-
(已锁定)
-
-