We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
request.query
The cookie is necessary only to compare the client.temporary(oauth_callback)'s result
client.temporary(oauth_callback)
bell/lib/oauth.js
Lines 67 to 73 in 9dbf61c
Do you have any insight?
This leads to having a set-cookie response header (occasionally) very big and the default NGINX config blocks it.
set-cookie
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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 resultbell/lib/oauth.js
Lines 67 to 73 in 9dbf61c
Do you have any insight?
This leads to having a
set-cookie
response header (occasionally) very big and the default NGINX config blocks it.The text was updated successfully, but these errors were encountered: