I am using a third party API which I send a GET request in Node JS and it responds with XML and an image encoded in base64.
I have tried looking for a third party module to split this out, but these all seem to work on a POST response.
Can Multer use the response from a GET to save the image?
Response is as follows:
--boundary
Content-Disposition: form-data; name="file.xml"; filename="file.xml"
Content-Type: text/xml
Content-Length: 1665
<XML>
.....
</XML>
--boundary
Content-Disposition: form-data; name="licensePlatePicture.jpg";
filename="licensePlatePicture.jpg"
Content-Type: image/jpeg
Content-Length: 7231
<BASE64 ENCODED IMAGE HERE>
I'm looking for an example of how to save the image without having to parse it manually.
Thanks.
Related
General context:
I am working on an IoT application where I upload images from an ESP32 connected to an SBC.
The uploading is done through an API provided by a third-party backend developer.
The upload API works through other mediums (such as Postman, python requests library, python http client library)
The ESP32 is connected to the SBC through UART.
I construct/generate the HTTP request on the SBC and send it as bytes. I have written a function on ESP32 that can send the bytes as a generic HTTP request, to the URL specified.
Then it sends the response string back to the SBC.
All of this works. For small requests, I am facing no issues. I am able to download images, etc.
However, when uploading an image, I don't get a response and I end up timing out after 30s. I checked without timeout FYI, but no response.
I checked from the server-side. It appears my request has succeeded and the server is sending me 200 with the URL of the image. Using that URL, I was able to verify that the image was uploaded successfully.
However, I do not receive this response on the microcontroller.
Not sure what the issue is. Any suggestions as to what I can do?
I can't give out the code but I'll send a general structure:
ESP32
-> Receives URL, port, length of request
-> Connects to server and reads the request from UART and writes to server
-> Wait for response after response is sent
Python raw http
POST (server path) HTTP/1.1
Host: (url)
correlation-id: test5
Content-Type: multipart/form-data; boundary=WebKitFormBoundary7MA4YWxkTrZu0gW
Authorization: Bearer (access token)
Content-Length: 268
--WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="portraits"; filename="name"
Content-Type: image/jpeg
(data)
--WebKitFormBoundary7MA4YWxkTrZu0gW--
Edit 1:
So, turns out it is not only "upload image", some other requests are also behaving similarly. Our server has many microservices. The services written in nodeJS which have more than 1 redirects are not working...?
I figured out what the issue is and hopefully, it will help anyone else facing the same issue. Also, some of my requests to the backend server which used a different authentication method worked
I had been generating the raw HTTP using postman code generation but it turns out Postman doesn't add a few headers which are needed for communicating with more complex servers.
What I mean is that if I host a local server, the above code will work. I had already tested it that way
What solved my problem is adding these headers:
POST (server path) HTTP/1.1
Host: (server URL)
User-Agent: ESP32
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
correlation-id: test
Authorization: Bearer (access_token)
Content-Length: 146360
Content-Type: multipart/form-data; boundary=af59ef02d60cd0efefb7bc03db1f4ffc
--af59ef02d60cd0efefb7bc03db1f4ffc
Content-Disposition: form-data; name="portraits"; filename="(name)"
Content-Type: image/jpeg
(data)
--af59ef02d60cd0efefb7bc03db1f4ffc--
I am using hapi for a simple API. I need to submit some data to a 3rd party api, with the data in a POST body, Content-Type: application/x-www-form-urlencoded in the header and the body containing the form data. I'm doing this successfully using form-data and node-fetch.
I'm writing a test for this using jest-fetch-mock to mock the fetch service. However, the mocked fetch request is a FormData() object, and to get the values of the body I have to use the form-data methods, specifically getBuffer(). The best I can do is get the text of the form data stream, which looks like this:
----------------------------873172308964049871716608
Content-Disposition: form-data; name="grant_type"
mockAuthorization_code
----------------------------873172308964049871716608
Content-Disposition: form-data; name="code"
mockAuthCode
----------------------------873172308964049871716608
Content-Disposition: form-data; name="redirect_uri"
redirectUrl.com/
----------------------------873172308964049871716608--
Is there any way I can parse these to test that the correct values are being submitted?
Thanks
I have tried creating an Apiary request with multipart/form-data, which seems alright, except when I try actually sending it via the console on Apiary to an existing (and functional) endpoint written in Node.js using async-busboy I'm getting back
{
"message": "Unexpected end of multipart data"
}
The Apiary Blueprint for this request looks like this:
+ Request
+ Headers
Content-Type: multipart/form-data; boundary=BOUNDARY
+ Body
--BOUNDARY
Content-Disposition: form-data; name="name"
John Doe
--BOUNDARY
Content-Disposition: form-data; name="email"
john.doe#email.com
--BOUNDARY--
I'd like to know if there is any problem that can be fixed in the Blueprint snippet or if this is even supported, or if the problem might be in the server itself (but the server works when I send a multipart post request from postman, curl and there are also few client implementations using it)
the HTTP preview:
POST /kflq_webcfg/v1/update HTTP/1.1
Host: h.innmall.cn
Cache-Control: no-cache
----WebKitFormBoundaryE19zNvXGzXaLvS5C
Content-Disposition: form-data; name="data"
{"orderInnerId":"12146","p":{"imei":"866568022978356","mac":"58:1f:28:ea:4d:e1","os":"android4.4.2","platform":"Android","ptype":"H60-L01_19_4.4.2","version":"6.1.1"},"type":1}
----WebKitFormBoundaryE19zNvXGzXaLvS5C
Content-Disposition: form-data; name="mode"
plain
----WebKitFormBoundaryE19zNvXGzXaLvS5C
But can parser x-www-form-urlencode:
POST /kflq_webcfg/v1/update HTTP/1.1
Host: h.innmall.cn
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
data={"orderInnerId":"12146","p":{"imei":"866568022978356","mac":"58:1f:28:ea:4d:e1","os":"android4.4.2","platform":"Android","ptype":"H60-L01_19_4.4.2","version":"6.1.1"},"type":1}&mode=plain
How to solve this problem through the body-parser middleware?
I need these two cases to get the same result.
thank you very much!
Body-parser cannot handle multipart bodies, you should use something like multer for that. In addition to handling file uploads multer also parses the text fields of a multipart data into req.body. Body-parser docs also give a good explanation.
I'm attempting to use the DocuSign REST API and create an OAuth request to execute Send of Behalf of (SOBO). Although I can't complete the first task, it's giving me back a Bad Request. What am I doing wrong?
Request with Headers:
POST https://demo.docusign.net/restapi/v2/oauth2/token
Accept: application/xml
Content-Type: application/xml
Content-Length: {length of body}
Request Body
<OAuthTokenRequest>
<grant_type>password</grant_type>
<client_id>{IntegratorKey}</client_id>
<username>test#email.com</username>
<password>{Password}</password>
<scope>api</scope>
</OAuthTokenRequest>
Response with Error:
400 Bad Request
<oauthErr xmlns="http://www.docusign.com/restapi" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<error>invalid_request</error>
<error_description>An OAuth2 error occurred:</error_description>
</oauthErr>
Although most of the DocuSign REST API accepts XML formatting, OAuth requests must be made in x-www-form-urlencoded.
Change your request to the following:
Request with Headers:
POST https://demo.docusign.net/restapi/v2/oauth2/token
Accept: application/xml
Content-Type: application/x-www-form-urlencoded
Content-Length: {length of body}
Request Body:
grant_type=password&client_id={IntegratorKey}&username=test#email.com&password={Password}&scope=api
Sample Response:
200 OK
<oauthAccess xmlns="http://www.docusign.com/restapi" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<access_token>{Access Token}</access_token>
<scope>api</scope>
<token_type>bearer</token_type>
</oauthAccess>
More information can be obtained in this documentation.