Hi,
I would like to understand why the cookie stores the request.query since they are not used furder in the code to accomplish the OAuth1 dance.
The cookie is necessary only to compare the client.temporary(oauth_callback)'s result
|
const state = { |
|
token: temp.oauth_token, |
|
secret: temp.oauth_token_secret, |
|
query: request.query |
|
}; |
|
|
|
h.state(cookie, state); |
Do you have any insight?
This leads to having a set-cookie response header (occasionally) very big and the default NGINX config blocks it.
Hi,
I would like to understand why the cookie stores the
request.querysince they are not used furder in the code to accomplish the OAuth1 dance.The cookie is necessary only to compare the
client.temporary(oauth_callback)'s resultbell/lib/oauth.js
Lines 67 to 73 in 9dbf61c
Do you have any insight?
This leads to having a
set-cookieresponse header (occasionally) very big and the default NGINX config blocks it.