BGS2T multipart file upload POST | Thales IoT Developer Community
August 29, 2014 - 2:31am, 6637 views
We are struggling with setting the correct values for doing a multipart file upload post from the BGS2T. With curl its as simple as the following:
curl -A "our_unique_user_agent_string" -F our_file=@our_local_file http://our_upload_url/
Looking at the backend that seems to set the content-type correctly as multipart/form-data. We can replicate this with the BGS2T by setting:
hcUsrAgent = "our_unique_user_agent_string"
hcProp = "Content-Type: multipart/form-data"
But how do we set the our_file property for actually sending the data during the AT command?
Any advice would be appreciated :)
Aug 29 2014 - 2:58pm
Hi,
let's assume that you want to send the files from this example from stack overflow:
http://stackoverflow.com/questions/4238809/any-example-of-multipart-form...
the module fills the request fields, but you have to properly fill the content. This means that you have to manually pass to the module all data after the line: Content-Length: 554 including boundary marker, content disposition parameter etc.
Best regards
Jedrzej
- Log in or register to post comments
Aug 29 2014 - 4:15pm
Thanks Jędrzej, thats exactly what we did and now have it working well. The trick is to pass in the multipart content-type with the boundary set:
hcProp = "Content-Type: multipart/form-data; boundary=---something_unique_here"
Then building the content manually:
---something_unique_here
Content-Disposition: form-data; name="our_file"; filename="whatever"
Content-Type: application/octet-stream
FILE_CONTENT->�������������
---something_unique_here--
And then to not to forget that hcContLen is then the whole length of the manually built content.
- Log in or register to post comments
Sep 1 2014 - 12:42pm
Hello,
great to see you got it working!
Regards
Jedrzej
- Log in or register to post comments
Sep 2 2014 - 10:23pm
We have run into a little problem though. For some reason we keep getting a 202 Error URC. Everything is received at the server and we are only sending the amount of bytes we set in hcContLen. Any ideas?
^SIS:.1,0,2201,"HTTP/1.0.200.OK"
^SIS:.1,0,202,"HTTP-ERR:.more.data.then."
- Log in or register to post comments
Sep 3 2014 - 1:12pm
Hi,
please check what's the state of the service after HTTP-ERR with AT^SISI?. Are you able to fetch the data after occurrence of the URC? ^SIS 202 indicates a server side issue, so it would be very helpful if you could provide wireshark traces from this communication.
Regards
Jedrzej
- Log in or register to post comments
Sep 3 2014 - 4:39pm
I sent the traces and code example via email. I will happily post our findings here but wireshark traces aren't so pleasant for a forum comment :)
- Log in or register to post comments
Sep 11 2014 - 8:49pm
Hello,
Please take a look at my configurationn. I've managed to send a file to http://posttestserver.com using multipart form. Hope you'll find this useful.
This is my Internet Service setup:
at^siss?
^SISS: 0,"srvType","Http"
^SISS: 0,"conId","0"
^SISS: 0,"alphabet","0"
^SISS: 0,"hcMethod","1"
^SISS: 0,"hcContLen","206" <- content length must match
^SISS: 0,"hcAuth","0"
^SISS: 0,"hcRedir","1"
^SISS: 0,"address","http://posttestserver.com/post.php"
^SISS: 0,"hcContent",""
^SISS: 0,"hcProp","Content-Type: multipart/form-data; boundary=------------------------583529263d0d78e3"
^SISS: 0,"user",""
^SISS: 0,"passwd","*****"
^SISS: 0,"hcUsrAgent","MC75/4.1"
^SISS: 0,"tcpMR","10"
^SISS: 0,"tcpOT","6000"
^SISS: 0,"secOpt",""
...
OK
This is my file content:
"--------------------------583529263d0d78e3
Content-Disposition: form-data; name="fname"; filename="f.txt"
Content-Type: text/plain
my test file content
--------------------------583529263d0d78e3--
"
And Internet Service execution:
at^siso=0
OK
^SISW: 0,1
at^sisw=0,206
^SISW: 0,206,0
<-- sending 206 bytes here
OK
^SISW: 0,2 <- no more data to be sent
^SIS: 0,0,2201,"HTTP/1.1 200 OK"
^SISR: 0,1 <- data received
at^sisr=0,1500 <- reading data
^SISR: 0,140
Successfully dumped 0 post variables.
View it at http://www.posttestserver.com/data/2014/09/11/07.29.24566211489
Post body was 0 chars long.
OK
^SISR: 0,2 <- no more data to be read
As you can see there is ^SISR URC informing about received data instead of ^SIS error message. Thanks to that I'm also able to read response content.
Regards
Jedrzej
- Log in or register to post comments