-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
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
reenable cookies in request so login will work again #21
Conversation
Cookies are now off by default in the current version of the request module: request/request#587 As a result, login no longer works. This reenables it.
Yeah login seems to be broken ;( Just noticed. |
There may be a better way to handle it, but this restores it to the way it was. I guess really each client should have its own cookie jar, but most of the time there is only one client anyway. |
Actually this should be better, having a new cookie jar for each instance of the api. |
reenable cookies in request so login will work again
Thanks for the fix, @kcivey! Was "broken" since request v2.23.0 |
I've tagged v0.3.7 which includes this fix and pushed the latest version of nodemw to NPM |
Awesome!! Thanks :) |
'use strict'; const azureHelper = require('./azure.helper'); /**
/**
/**
/**
/**
/**
module.exports = new azureModule(); This global jar:true hitting very badly :(, Any help would be appreciated If I disable jar: true it is not carrying the cookies to other call so it is getting failed , If I enabled it is always considering as old client even for new instance hit |
Cookies are now off by default in the current version of the request module:
request/request#587
As a result, login no longer works. This reenables it.