HttpResult gets a set-cookie instead of a cookie

summer · Posted on 5/29/2019 10:40:12 AM

Why do I use HttpResult to get set-cookie instead of cookie, how can I get the value of the cookie?

Little scum · Posted on 5/29/2019 9:37:32 PM

The default lifetime of a cookie ends when the browser is closed. The domain name that can be accessed is under the created domain name and its subdomains, and the path that can be accessed is under the created path and its subpaths, which can be changed by setting the attributes

The Set-Cookie response header is returned by the serverResponse headA cookie used to store a cookie in the browser, once placed, will automatically bring this cookie when the browser accesses the eligible URL address

Set-Cookie: cookie1=val1; Expires=?; Domain=?; Path=?

set-cookie is actually a cookie, which contains a cookie, domain, expiration time, and path.

However, when you make a request, you only need to bring the cookie value, as shown in the figure below:

[New Issue] HttpResult gets a set-cookie instead of a cookie

Related Posts

Sections viewed