On sexta-feira, 29 de julho de 2016 14:53:40 PDT ???(Uze Choi) wrote:
> Some of reasons are independent from incremental release
> and the others are invalid if HTTPS support does not affect CA layer.
Let me go over them again, in priority order:
* some websites require HTTPS
The only way to access those sites is to have the support
* websites that do have HTTPS should be accessed as HTTPS, even if they
provide HTTP support
This again requires that we implement it
* a well-known HTTP library will implement HTTP better than the code currently
proposed
This is actually an argument against the proposed implementation, not
really in favour of HTTPS. However, any good HTTP library implements
HTTPS, therefore we get HTTPS support "for free"
* there will be an architectural change if we do HTTP first then HTTPS
I agree that if the implementation can be done without architectural
change, this reason goes away. So can someone show me the architecture
and proof of concept for the proxy with HTTPS support?
* using a third-party library will make some CA changes unneeded
Same as the preivous one. I want to see the design and PoC for HTTPS
support.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
