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
Resty Debug doesn't reflect all of the cookies that are being used.
After using resty to make an API authorization, my API's server responds with a Set-Cookie: which Resty handles excellently. The presence of the new cookies is verified in the current client's cookie jar, e.g. the below has plenty of output, including the API's authorization token.
However, when using Debug mode with Resty, those cookies are not present in the next API call, making the output misleading as we are sending more to the server than the log would have me believe, e.g. note the HEADERS in the response log from the following.
Resty Debug doesn't reflect all of the cookies that are being used.
After using resty to make an API authorization, my API's server responds with a
Set-Cookie:
which Resty handles excellently. The presence of the new cookies is verified in the current client's cookie jar, e.g. the below has plenty of output, including the API's authorization token.However, when using Debug mode with Resty, those cookies are not present in the next API call, making the output misleading as we are sending more to the server than the log would have me believe, e.g. note the
HEADERS
in the response log from the following.The text was updated successfully, but these errors were encountered: