The pit that the response message does not change after postman modifies the url

1. Brief introduction

Recently, I joined the debugging interface with other systems, and used postman to request the opposite url, and the result returned 401;

After fixing the bug on the opposite side, let me try another url (the content of the request parameter has not been changed at that time);

As a result, it still returns 401 all the time.

The connection and debugging failed, so I asked the other person to fix the bug, and the other person checked for a long time. If there is no bug, I can adjust it myself.

Finally, I changed the url in the code to call the opposite interface, and found that it can indeed be adjusted, but at this time, using the same url and parameters in postman still returns 401, which is very embarrassing.

Two, the cause of the problem

Obviously, postman cached the last returned result;

Although the url is changed , but the parameters are not changed , postman keeps returning the cached results, which makes people mistakenly think that there are still problems with the interface and that it is not connected.

3. Solutions

1. Don't just change the url, but also change the content of the parameters (this should work)
2. Restart postman
3. Restart the computer

Guess you like

Origin blog.csdn.net/BHSZZY/article/details/131271100