You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional Information
Editing the cookie value from the cookie manager window to add an equal character at the end, before doing the request, works fine. But that only works once, because the client will drop the character again after every response.
According to page 8 in RFC6265, the 0x3d (=) character is permitted for the cookie value:
Hi!
Actual vs Expected Behavior
The server replied with a cookie in its response, and looked like this:
set-cookie: foo=bBRrE9bLezh+bRbQr7jBRd+4jfM7iCrsxe0s1fr4f3I=; Path=/; SameSite=Lax
however, the next request from the Advanced REST Client, dropped the trailing equal character, and the request header looked like this:
cookie: SameSite=Lax; foo=bBRrE9bLezh+bRbQr7jBRd+4jfM7iCrsxe0s1fr4f3I
when it should have looked like this:
cookie: SameSite=Lax; foo=bBRrE9bLezh+bRbQr7jBRd+4jfM7iCrsxe0s1fr4f3I=
Additional Information
Editing the cookie value from the cookie manager window to add an equal character at the end, before doing the request, works fine. But that only works once, because the client will drop the character again after every response.
According to page 8 in RFC6265, the 0x3d (=) character is permitted for the cookie value:
The text was updated successfully, but these errors were encountered: