restler | REST client library for node.js | JSON Processing library
kandi X-RAY | restler Summary
kandi X-RAY | restler Summary
Restler
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Initialize a new Request with the given options
- Send JSON request
- Initialize a new Stream
- An instance of Service .
- Mix one object into another .
- File constructor
- Helper method to shortcut options
- Make a request
- A multipart request .
- A data representation of a single file .
restler Key Features
restler Examples and Code Snippets
var _ = require('lodash'),
restler = require('restler'),
CM = require('cookie-manager'),
cm = new CM();
var url = 'https://' + host1 + '/page';
restlerOptions = {
//Set the cookie for host1 in the request header
Community Discussions
Trending Discussions on restler
QUESTION
I am writing an application in node.js which will need to make http requests to external websites, and will need to include the ability to login and manage the cookies from these sites so that the session id is always present in any subsequent request headers.
When performing similar tasks in Java, this was straightforward using the java.net.CookieHandler & java.net.CookieManager, together with java.net.HttpURLConnection to make the requests (I can provide sample code for this is it's useful, but don't want to confuse this thread too much for now since the focus should be on the node.js implementation): every time a request is made, the cookie is correctly updated and maintained based on the Set-Cookie response headers as expected.
For the node.js application I am attempting to use restler for httq requests ^3.2.2, and cookie-manager ^0.0.19. This seems to require manually setting the cookie in the request header when sending each request, and updating the cookie based on the response headers whenever a request is completed. Sample code for a login request:
...ANSWER
Answered 2020-Apr-23 at 11:031) To prevent automatic redirect follow-up with POST, I had to add "followRedirects: false" to the initial request options, and then manually resubmit a GET request if the response code was one of [301,302,303].
2) Since redirects are being done manually, I was able to manually set the cookie based on the new domain on each request.
3) There was no need to extract values from each "Set-cookie" header and append them into a single string - cookie-manager does this automatically.
New code which works (combining fixes 1,2,3 above):
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
Install restler
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page