-
Notifications
You must be signed in to change notification settings - Fork 235
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
Buffer #43
Comments
It's a string or binary buffer, depending on what you requested. In most cases you'd just do Is that what you mean? |
Well the problem is that I know for sure that the request should take 3 to 5 minutes to get a response and this is what I get after 20 seconds; as if it is prematurely timing out. (even if timeout option is set to 0). |
And what do you get with I can see that the response is empty (0 bytes) though. Unless the first argument is an Error, it means that the request was successful. |
The request I'm sending creates virtual machines and the response has the credentials. I've just run out off space though and I don't have the permissions to delete; so I'll have to test again tomorrow. |
Sure, let me know if there's any way I can help. |
Hi, were you able to take a look at this? |
Yes I did. It seemed to be a problem with the external service; not Needle. |
When I send a POST request I'm getting back a Buffer in the request body. How do I handle this?
{ ...
resume: [Function],
read: [Function],
bytes: 0,
body: < Buffer > }
The text was updated successfully, but these errors were encountered: