Preface
Briefly introduce the status bar and quick exec.
Text
Introducing debug front , Introduce to you quick exec:
This is the command tool .
We can execute some commands to achieve our effect .
There is a line in it , Input help Learn more .
help Then a new web page will open .
There are some commands ：
For example, this search .
If you are interested, you can have a look at ：https://docs.telerik.com/fiddler/knowledge-base/quickexec
Then we mainly talk about a breakpoint . I introduced , The global breakpoint is set as follows .
Then it must not be done .
This command can specify a string containing , Conduct debug.
In this way, we can accurately specify what we want .
In the input bpu dada, And then go back .
You can see ：
Then you find that there is no breakpoint , Why is this ？
It's actually being encode 了 .
When I introduced the tool earlier , The following :
We can escape .
Then input :
Once again .
This matches .
So how to clear breakpoints ？
Take another look at the status bar :
This means that we activate capture , If you click it, it will cancel the capture , As mentioned before F12, Shortcut key .
The second is that you can quickly select the process .
If you are debugging your own company's software , Then it's not a browser , It can be filtered out .
This is the breakpoint , Don't need to say more .
I haven't used the above one either , How many are there on the right , On the left is the selected number , It's not what it takes. .
And then the breakpoint debug I don't use this much , Generally speaking, the backend verifies the correctness of the interface ,composer That's all right. .
Here I will simply post what others wrote ：https://www.jianshu.com/p/a4bc71c4fd85, It's very detailed .
junction
In the next section, I will simply sort it out , How to grab https Packet and weak network testing .
