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
encoding support in options #16
Comments
🆙 for this issue |
Hi...
Keep in mind that See pull request #29 |
how do you set the responseType in this browser-request module? there do you put this? |
Hi .. it seems a lot of pull requests haven't been added in here. |
@yegodz ok, a few questions then: 1. does "npm install browser-request" install your version? or should I download it manually? |
I haven’t uploaded to npm yet (meaning to do so sometime :-) For now, just download and use it from Github. I will be updating the documentation on github shortly, but meanwhile, you can do two things:
Some extra options are available to be added to the ‘options’ object that is passed to request
Support for Multipart/related uploads
Support for multipart/formData file upload
Ruchir Godura Keep your cloud data private at http://www.xooui.com http://www.xooui.com/
|
Hey. Thank you for the examples!
Is this module supposed to handle also SENDING binary data? |
Not really … if you use Chrome, you can look at the dev tools and actually capture every HTTP request as it goes out.
Ruchir Godura Keep your cloud data private at http://www.xooui.com http://www.xooui.com/
|
Thanks for the advice!. Tried all the things, didnt work. Now I got one hypothesis and this seems to be the case: google sends 400 if I send any cookies in that request(chrome adds automatically cookies relevant for the domain). |
yes.. that is one more difference between the browser and node.js is that the browser will automatically send any relevant cookies whereas node will only send those that you explicitly add to the request. Ruchir Godura Keep your cloud data private at http://www.xooui.com http://www.xooui.com/
|
Yeah, in the end the problem was with the cookie. Thanks for the examples:) |
The latest request has an option 'encoding' which allows getting files as buffers or at least, bypassing the conversion to unicode. This option is not present in browser-request not does it warn the user about it.
The text was updated successfully, but these errors were encountered: