Please do not block the enthusiasm to provide the solution for non HTTPS website. CA is not affected from it. Please do not concern. -----Original Message----- From: Thiago Macieira [mailto:[email protected]] Sent: Friday, July 29, 2016 3:28 PM To: ???(Uze Choi) Cc: ashok.channa at samsung.com; iotivity-dev at lists.iotivity.org Subject: Re: [dev] CoAP - HTTP Proxy Review Request
On sexta-feira, 29 de julho de 2016 15:22:35 PDT ???(Uze Choi) wrote: > Front some reasons are related with capability. > Incrementally we can extend the web site coverage scope. Yes, we could. I am saying that doing it incrementally is not acceptable for me. The first version that lands on the master branch must be feature-complete, meaning it needs to include HTTPS support. It can be developed incrementally in a branch. > From later parts, your concern looks CA change. > Without it, you should not raise issue. Yes, I am concerned with the implementation. I think that the implementation would be more stable and more robust with a third-party HTTP stack, not just the HTTP header parser. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
