Hi Dan,

I attach the log. Please help to take a look.

Thanks

Tuan Nguyen
________________________________
From: Daniel Stenberg <dan...@haxx.se>
Sent: Tuesday, September 17, 2019 2:57 PM
To: Nguyen Hoang Tuan (Hubble Vietnam) via curl-library 
<curl-library@cool.haxx.se>
Cc: Nguyen Hoang Tuan (Hubble Vietnam) <nguyen.t...@hubblehome.com>
Subject: Re: Curl coredump after re-use connection

On Tue, 17 Sep 2019, Nguyen Hoang Tuan (Hubble Vietnam) via curl-library wrote:

> Please help to review what I miss.

It looks like you're not telling curl how large your post content is and
you're not asking for it to get done with Chunked encoding. I think curl can
only close the connection after that post is done as a signal to the server
that it is complete.

--

  / daniel.haxx.se | Get the best commercial curl support there is - from me
                   | Private help, bug fixes, support, ports, new features
                   | https://www.wolfssl.com/contact/
d->version_num 470784
post_request infor: address https://bt-r1-staging-cs.hubble.in/v7/devices/child_devices/register.json?auth_token=XXXXXXXXXXXX, data [{"name":"Cam-0681B958CA","registration_id":"010681AC5D5CB958CALXWJJIKI","firmware_version":"03.30.00","talkback_port":"51108","mac_address":"AC5D5CB958CA","time_zone":"+07.00"}]
reuse
*   Trying 52.206.60.166...
* Connected to bt-r1-staging-cs.hubble.in (52.206.60.166) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: ./certs.pem
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*    subject: OU=Domain Control Validated; CN=*.hubble.in
*    start date: Oct 23 06:14:20 2018 GMT
*    expire date: Oct 22 08:08:25 2020 GMT
*    subjectAltName: bt-r1-staging-cs.hubble.in matched
*    issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*    SSL certificate verify ok.
> POST /v7/devices/child_devices/register.json?auth_token=XXXXXXXXXXXXXX HTTP/1.1
Host: bt-r1-staging-cs.hubble.in
Accept: */*
Content-Type: application/json
Connection: keep-alive
User-Agent:0680/03.30.00
Content-Length: 178

* upload completely sent off: 178 out of 178 bytes
< HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Origin, X-Requested-With, Authorization, accept, content-type, X-Auth-Tenant,X-Application-Id,X-Application-Platform,X-Auth-Username,X-Auth-Password,X-Auth-Token,X-Auth-Token-Type,X-Application-Id,X-Refresh-Token,X-Response-Code
< Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
< Access-Control-Expose-Headers: X-Response-Code ,X-UniqueRegistrationId
< Content-Security-Policy: default-src 'self' *.hubble.in;img-src 'self' *.hubble.in;script-src 'self' 'unsafe-inline' *.hubble.in
< Content-Type: application/json
< Date: Tue, 17 Sep 2019 07:51:15 GMT
< Strict-Transport-Security: max-age=31536000
< X-Application-Context: application:bt-r1-staging:8080
< Content-Length: 151
< Connection: keep-alive
< 
* Connection #0 to host bt-r1-staging-cs.hubble.in left intact

time_namelookup: 0.1
time_connect: 0.3
time_appconnect: 0.8
time_pretransfer: 0.8
time_redirect: 0.0
time_starttransfer: 1.5
time_total: 1.5
do not free
result = 
get_request infor: address https://bt-r1-staging-cs.hubble.in/BMS/cameraservice?action=command&command=success_update&version=03.30.00&auth_token=XXXXXXXXXXXXX
reuse
start perform
* Found bundle for host bt-r1-staging-cs.hubble.in: 0x22958c0 [can pipeline]
* Hostname bt-r1-staging-cs.hubble.in was found in DNS cache
*   Trying 52.206.60.166...
* Connected to bt-r1-staging-cs.hubble.in (52.206.60.166) port 443 (#1)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: ./certs.pem
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*    subject: OU=Domain Control Validated; CN=*.hubble.in
*    start date: Oct 23 06:14:20 2018 GMT
*    expire date: Oct 22 08:08:25 2020 GMT
*    subjectAltName: bt-r1-staging-cs.hubble.in matched
*    issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*    SSL certificate verify ok.
> GET /BMS/cameraservice?action=command&command=success_update&version=03.30.00&auth_token=XXXXXXXXXXXXXXXXX HTTP/1.1
Host: bt-r1-staging-cs.hubble.in
Accept: */*
Content-Type: application/json
Connection: keep-alive
User-Agent:0680/03.30.00

< HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Origin, X-Requested-With, Authorization, accept, content-type, X-Auth-Tenant,X-Application-Id,X-Application-Platform,X-Auth-Username,X-Auth-Password,X-Auth-Token,X-Auth-Token-Type,X-Application-Id,X-Refresh-Token,X-Response-Code
< Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
< Access-Control-Expose-Headers: X-Response-Code ,X-UniqueRegistrationId
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate
< Content-Security-Policy: default-src 'self' *.hubble.in;img-src 'self' *.hubble.in;script-src 'self' 'unsafe-inline' *.hubble.in
< Content-Type: text/html
< Date: Tue, 17 Sep 2019 07:51:16 GMT
< Expires: 0
< Pragma: no-cache
< Strict-Transport-Security: max-age=31536000
< Vary: Accept-Encoding, User-Agent
< X-Application-Context: application:bt-r1-staging:8080
< X-Content-Type-Options: nosniff
< X-Frame-Options: DENY
< X-XSS-Protection: 1; mode=block
< Content-Length: 30
< Connection: keep-alive
< 
* Connection #1 to host bt-r1-staging-cs.hubble.in left intact

time_namelookup: 0.0
time_connect: 0.2
time_appconnect: 0.8
time_pretransfer: 0.8
time_redirect: 0.0
time_starttransfer: 1.1
time_total: 1.1
do not free
ret = 0
result = Firmware upgraded successfully
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Reply via email to