Posted on May 03, 2017 at 13:55After quite lot of debugging I still cannot get this working. I suspect the problem is how I split the multipart transfer. First I tought the problem was after the header and middle of body, however I can get the problem appear just by sending the header and waiting a moment for server response (using Expect: 100-continue like Curl does).
The curl that I'm trying to emulate is(
https://miguelmota.com/blog/alexa-voice-service-with-curl/
:(
curl -v -o log.txt -X POST \
-H 'Authorization: Bearer ${TOKEN}' \
-H 'Content-Type: multipart/form-data; boundary=${BOUNDARY}' \
--data-binary @multipart_body.txt \
https://community.st.com/external-link.jspa?url=https%3A%2F%2Faccess-alexa-na.amazon.com%2Fv1%2Favs%2Fspeechrecognizer%2Frecognize
I can do less than 1k transfers and receive data OK.
Current iteration of the socket communication:
1. I send the header:
const static char *synth_header = 'POST /v1/avs/speechrecognizer/recognize HTTP/1.1\r\n\
Host: access-alexa-na.amazon.com\r\n\
Authorization: Bearer %s\r\n\
Content-Type: multipart/form-data; boundary=BOUNDARY1234\r\n\
Transfer-Encoding: chunked\r\n\
Cache-Control: no-cache\r\n\r\n';
Second I send the first part of payload (json):
const static char *synth_payload = '--BOUNDARY1234\r\n\
Content-Disposition: form-data; name=\'metadata\'\r\n\
Content-Type: application/json; charset=UTF-8\r\n\
\r\n\
{\'messageHeader\': {},\'messageBody\': {\'profile\': \'alexa-close-talk\',\'locale\': \'en-us\',\'format\': \'audio/L16; rate=16000; channels=1\'}}\r\n\r\n';
As this is first chunk I've added the size before above payload in hex:
fa
--BOUNDARY1234
Content-Disposition: form-data; name='metadata'
Content-Type: application/json; charset=UTF-8
{'messageHeader': {},'messageBody': {'profile': 'alexa-close-talk','locale': 'en-us','format': 'audio/L16; rate=16000; channels=1'}}
And after that next part of the payload + audio data.
My question is that does the wifi module add the chunk size by default, so am I messing up things by manually adding this to sent data. Any ideas how the chunked multipart transfer should be handled with this module? I've verified the token I get from Amazon with curl so that should be OK. And as I said, if I use 'Expect: 100-continue' in the first header and wait for the server to ack my transfer I first get 100 continue and right away 400 error. So something is wrong with the header packaging.
BTW: is there way round the 1k max transfer forced by the library? Is this limitation by the wifi module?
