upload http_client

RE: upload http_client

Martin Lesund — Tue, 14 Apr 2020 11:40:24 GMT

Since you do not want to use TLS, you can set that to None.

RE: upload http_client

Shekhar Suthar — Mon, 06 Apr 2020 10:10:45 GMT

hey Martin Lesund

[quote userid="66115" url="~/f/nordic-q-a/59432/upload-http_client/243388"]Try to set none to the verification.[/quote]

That thing worked for me Thank you for your help

So can you explain me that why we did this? seems like this is not a ideal way so.

RE: upload http_client

Martin Lesund — Fri, 03 Apr 2020 11:53:52 GMT

Try to set none to the verification.

Please share the full code so I could try to reproduce the issue.
(We can make this case private if there is sensitive information)

RE: upload http_client

Shekhar Suthar — Mon, 30 Mar 2020 14:37:25 GMT

hey Martin Lesund

I want get and post some JSON data on a server by http protocol with is secure but I'm getting this error

RE: upload http_client

Martin Lesund — Mon, 30 Mar 2020 14:17:45 GMT

Q1: For HTTPS it is.

It does sound like you want to connect just to a server using HTTP?
Are you aware of the difference between HTTP and HTTPS?
You could use regular HTTP if you do not want to use certificates for security.

Q2: This is most likely caused by something else. Cannot say without any serial logs etc. Try to enable debug logs from the necessary modules.
note that for the https sample you would also need to change the hostname another place in the code as well.

RE: upload http_client

Shekhar Suthar — Mon, 30 Mar 2020 13:04:03 GMT

Que1) is that necessary to give any certificate for HTTPS connection by nRF9160 ?

Is there any option with out certificate and fingerprints may be ??

Que2) if I used this URL the device rebooting again and again it not even enter in main()

RE: upload http_client

Martin Lesund — Mon, 30 Mar 2020 12:49:42 GMT

It depends on what you want to achieve. e.g Default sample connects to www.google.com which needs a X.509 certificate provided in the samples/nrf9160/https_client/cert folder.

Connect to your own server, what type of server?
--> To connect to other servers, you might need to provision a different certificate. You can download a certificate for a given server using your web browser. Alternatively, you can obtain it from a dedicated website like SSL Labs.

Then you can put the certificate in PEM format as instructed in the doc.

The certificate is provisioned in the cert_provision() function

Where do you put this "URL"? Please provide more details to help me understand the issue.

RE: upload http_client

Shekhar Suthar — Mon, 30 Mar 2020 12:16:53 GMT

hey Martin Lesund thank for you time
tell me some other way to get this because in this we need ROOT_CA certificate right ?? an I don't think so this is ideal ans some security issue

One more thing I want to know that do we have length limits of URL because when I used a long URL (100+ char) to get JSON its reboot device ?

RE: upload http_client

Martin Lesund — Mon, 30 Mar 2020 12:05:49 GMT

Hi Shekhar,

Let us focus on one sample at the time and try to make that work.

The HTTPS client sample from the official NCS repo.

It's hard to say what the exact issue is without more information.

What changes have you done to the default sample?

This is the output from running the default sample:

RE: upload http_client

Shekhar Suthar — Mon, 30 Mar 2020 08:05:12 GMT

any update Martin Lesund

RE: upload http_client

Shekhar Suthar — Mon, 30 Mar 2020 08:03:07 GMT

can someone help me out ????

RE: upload http_client

Shekhar Suthar — Fri, 27 Mar 2020 09:51:38 GMT

hello Nordic DevZone

I'm stilling facing the same issue, I'm trying with 3 4 url to get some results but all time the result s same as here in image.

as per I got two different example and I tried both of them and the link are here > example1 example2

one more thing I want to know that do we have length limits of url because when I used a long url to get JSON its reboot device ?

So please help me out

RE: upload http_client

Shekhar Suthar — Thu, 26 Mar 2020 15:11:20 GMT

hey Martin Lesund

I'm using that example here
it's seems like they need me to put Root-CA certificate pi pem format .

I'm still looking answer for que C) in my last post

Yes, looked here (It has a section on how you obtain a certificate.)

RE: upload http_client

Martin Lesund — Thu, 26 Mar 2020 14:42:46 GMT

Hi,
Have you looked at the sample documentation?

It has a section on how you obtain a certificate.

(And it can be provisioned in different ways.)

RE: upload http_client

Shekhar Suthar — Thu, 26 Mar 2020 06:45:44 GMT

I hope that error was over some and now I got output like this

A) that mean now its runing and waiting for ROOT-CA certificate and in example there is certificate so that will work or I need to change that ???

B) we all know NO one like to put ROOT_CA certificate so is there any other way to work on that like if we can use fingerprint ???

C) Is that necessary to use that certificate in code as per example ???

RE: upload http_client

Lukáš — Wed, 25 Mar 2020 21:42:56 GMT

We have the same issue with SES 4.42a. We are not able to write multiple times. After first firmware writes, it breaks up and you need to use nRF Prog to erase the flash. Then you can write again. SES 4.30 works well.

RE: upload http_client

Martin Lesund — Wed, 25 Mar 2020 15:32:52 GMT

Hi,
Please make sure to erase the flash before you flash a new image to make sure there is no "garbage" in the flash to affect this.
Are you flashing the merged.hex file?
Are you able to flash the precompiled applications in the .zip folder?

RE: upload http_client

Shekhar Suthar — Wed, 25 Mar 2020 07:00:34 GMT

hello Didrik Rokhaug I followed your mentioned step and get the the output as in image again and again I thing device is rebooting its not able to enter in main() .

I'm uploading https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/samples/nrf9160/https_client/src/main.c

I'm reading various technical blogs regarding that but not getting the proper reason behind that hope you can help me on that too

RE: upload http_client

Didrik Rokhaug — Tue, 24 Mar 2020 12:54:07 GMT

Do you mean a guide for how to use the Programmer application with the nRF91 DK?

We do not have that at the moment, as far as I know.

However, we do have such a guide for the Thingy:91: https://infocenter.nordicsemi.com/topic/ug_thingy91/UG/thingy91/firmware_update/updating_app_fw_nRF9160_debugprobe.html

Step number 2 and 4a are not necessary for the DK, as there is an on-board debugger. In step 4c, you should choose the entry for the nRF91 DK (PCA10090).

RE: upload http_client

Shekhar Suthar — Tue, 24 Mar 2020 12:01:19 GMT

Thanks Didrik Rokhaug for you response.

what about if I want to use nRF connect can you send me any link Doc to upload my hex file in nRF9160

RE: upload http_client

Didrik Rokhaug — Tue, 24 Mar 2020 11:45:44 GMT

Hi.

We are aware of several problems with Segger Embedded Studio v4.4.2 (Nordic Edition). We are working on solving them and should have a new version available soon.

When using the Programmer application to flash the device, you should use the merged.hex file found in <your build folder>/zephyr.

You should be able to solve your problem by issuing an erase-all before programming. If you are using nrfjprog from the command line, the command would be "nrfjprog -e".

Best regards,

Didrik