Why can't I put the cookie in the Request Header using tools?

Assume that only one COOKIE is saved after a website is logged on and is considered as logged on. Then, when I use FIREBUG for a request, I can see that the COOKIE is carried in the request header, but I can't figure out where to put the COOKIE in the Request Header using a tool. Isn't it because the cookie is not in the request hair?... assume that only one COOKIE is saved after a website is logged on and is considered as logged on. Then, when I use FIREBUG for a request, I can see that the COOKIE is carried in the request header, but I can't figure out where to put the COOKIE in the Request Header using a tool. Isn't it because the cookie is not in the request hair? But why does FIRBUG be visible in the request header?

Reply content:

Assume that only one COOKIE is saved after a website is logged on and is considered as logged on. Then, when I use FIREBUG for a request, I can see that the COOKIE is carried in the request header, but I can't figure out where to put the COOKIE in the Request Header using a tool. Isn't it because the cookie is not in the request hair? But why does FIRBUG be visible in the request header?

Incomplete package

Is your cookie domain name set correctly? Or you can write a small demo to test it.

What do you mean.
The backend server has many ways to reject your request, not just a cookie, but a simple referer parameter.

It should be that all the parameters in the header are included and requested in the corresponding request method. cookie is only a parameter in the header.

Run the curl copied from the chrome debugging tool on the linux Command Line to simulate a request sent by the browser. The figure is big and you can click it to see it, so there is no need to use other tools. This method is quite good.