[OE-core] [PATCH] send-error-report: Use https instead of http protocol

[Robert Yang]

On 3/4/19 6:26 PM, Richard Purdie wrote:
> On Mon, 2019-03-04 at 18:02 +0800, Robert Yang wrote:
>> Hi RP,
>>
>> On 3/4/19 5:23 PM, Richard Purdie wrote:
>>> On Mon, 2019-03-04 at 15:50 +0800, Robert Yang wrote:
>>>> Hi Khem,
>>>>
>>>> We have an internal error web server, this patch breaks it:
>>>>
>>>> You're accessing the development server over HTTPS, but it only
>>>> supports HTTP
>>>>
>>>> So I tried to use runsslserver, but it doesn't work either since
>>>> the
>>>> host is
>>>> Ubuntu 14.04 (python 2.7.6):
>>>>
>>>> $ python manage.py runsslserver
>>>>
>>>> [snip]
>>>>        ssl_version=ssl.PROTOCOL_TLSv1_2,
>>>> AttributeError: 'module' object has no attribute
>>>> 'PROTOCOL_TLSv1_2'
>>>>
>>>> This is because python is old.
>>>>
>>>> I think that make it default to https would make the server
>>>> harder to
>>>> set up,
>>>> so is it possible to:
>>>>
>>>> * Make it default to http, and add an option such as --https (or
>>>> --
>>>> ssl) for https
>>>>
>>>> Or:
>>>>
>>>> * Add an option such as --no-ssl to make it use http.
>>>>
>>>> I prefer the first one since https server is harder to setup than
>>>> http in django. I can work on it if no objections.
>>>
>>> At this point the project does require python3 so python2 being old
>>> shouldn't be a reason to be changing this.
>>
>> The python3 + error-report-web doesn't work for me:
>>
>> $ python3 manage.py runserver ip:8000
>>
>> And when I tried to access http://128.224.156.132:8000, it raised
>> errors:
>>
>> error-report-web/Post/views.py", line 16, in <module>
>>       from parser import Parser
>> ImportError: cannot import name 'Parser'
>>
>> So I use python 2 for it. I thought that it didn't support python3,
>> or didn't
>> test well.
> 
> Fixing it to work with python3 would be the preferred option...

Sounds good, I will work on it.

// Robert

> 
> Cheers,
> 
> Richard
> 
>