backend set up by express
Cross-domain request. The request header of set-cookie cannot be seen in chrome browser network, but edge can.
however, although chrome cannot view the set-cookie, the background of the second request can read the previously set cookie from the request.
the request header across domains has been set, and ajax has also set the request
cookie
edge
edgecookie
express
chromeset-cookie
did you step on the wrong spot?
I suspect that this is intentional by chrome, because cross-domain cookie cannot be operated with js, so it doesn't make much sense.
if you really want to see it, you can read it in application.
is cross-domain, and the same origin policy
ajax credentials
is the same origin policy, which can be put under different ports of the same domain name or under the subdomain name. It cannot be operated under different domain names.
you can try two different domain names here. Online and localhost are different
check the request header with fiddler. It is true that there is a
in the set-cookie field. Since cookie, is indeed set and subsequent requests can also get the cookie, it seems that chrome deliberately hides this field.
throw the pot at chrome for the time being, and then reverse the case later when you have other conclusions.
I am exactly like you. The backend
access-control-allow-origin
access-control-allow-credentials
is also set, and the withCredentials of the front end ajax is also set, but the set-cookie and cookie, can not be seen in network, while firefox can see
Previous: Css if the navigation bar switch, underline caterpillar switch effect?
Next: The user thread can do its own thing without waiting. What can the user thread do without data?
