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
Right now there's no support for using a proxy at all.
The underlying reason is that 'get-promise' uses the core 'http' and 'https', which require a bit of effort to use with proxies.
And the package doesn't even try.
Also doesn't seem to be actively maintained or used by much of anything I've seen (though I'm a relative newbie in Node-land)
I suspect it might be better to move to a different way of making the requests entirely, if proxies should be supported (and I'd like it to be).
The text was updated successfully, but these errors were encountered:
I chose get-promise mostly for its size. But maybe request-promise is worth a try.
I don't know how much it would increase the overall download size
Am 17. Februar 2017 03:36:37 MEZ schrieb Philipp Hanes <notifications@github.com>:
Right now there's no support for using a proxy at all.
The underlying reason is that 'get-promise' uses the core 'http' and
'https', which require a bit of effort to use with proxies.
And the package doesn't even try.
Also doesn't seem to be actively maintained or used by much of anything
I've seen (though I'm a relative newbie in Node-land)
I suspect it might be better to move to a different way of making the
requests entirely, if proxies should be supported (and I'd like it to
be).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#23
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Right now there's no support for using a proxy at all.
The underlying reason is that 'get-promise' uses the core 'http' and 'https', which require a bit of effort to use with proxies.
And the package doesn't even try.
Also doesn't seem to be actively maintained or used by much of anything I've seen (though I'm a relative newbie in Node-land)
I suspect it might be better to move to a different way of making the requests entirely, if proxies should be supported (and I'd like it to be).
The text was updated successfully, but these errors were encountered: