Yikes, I just added some technical info to the Jira ticket:

Seeing it working from Firefox but Digicert agrees it is expired from
their SSL testing tool, https://www.digicert.com/help/ shows the TLS
cert expired on 4/24/2020

DNS resolves echarts.apache.org to 13.107.246.10

HTTP Server Header: Apache/2.4.18 (Ubuntu)
TLS Certificate

Common Name = echarts.apache.org

Subject Alternative Names = echarts.apache.org

Issuer = DigiCert SHA2 Secure Server CA

Serial Number = 0FCEF55C8F3D01B48D6CA2EA0CCF56CE

SHA1 Thumbprint = 8CEFE6D13DAF704C4A1EAC3862D1D6CD53CC3035

Key Length = 2048

Signature algorithm = SHA256-RSA

Secure Renegotiation:
TLS Certificate has not been revoked
OCSP Staple:     Not Enabled
OCSP Origin:     Good
CRL Status:     Good

TLS Certificate is expired.

The certificate was valid from 24/Apr/2019 through 24/Apr/2020.
Certificate Name matches echarts.apache.org
Subject    echarts.apache.org
Valid from 24/Apr/2019 to 24/Apr/2020
Issuer    DigiCert SHA2 Secure Server CA
     
Subject    DigiCert SHA2 Secure Server CA
Valid from 08/Mar/2013 to 08/Mar/2023
Issuer    DigiCert Global Root CA

On 4/26/2020 12:37 AM, Ovilia wrote:
> Yesterday, we noticed that ECharts apache Website domain has an HTTPS CA
> expired error and blocking users from accessing it.
>
> We reported this on JIRA [1] and this has not been fixed for now. So we
> temporarily cancelled the redirection from echartsjs.com to
> echarts.apache.org.
>
> [1] https://issues.apache.org/jira/browse/INFRA-20185
>
> Thanks
>
> Wenli
>
>
> On Tue, Apr 21, 2020 at 4:39 PM Ovilia <oviliazh...@gmail.com> wrote:
>
>> Shuang Su has just redirected echartsjs.com to echarts.apache.org.
>> If anyone find the speed is slow, please let us know.
>>
>> Thanks
>>
>> Wenli
>>
>>
>> On Tue, Apr 21, 2020 at 1:27 PM Ovilia <oviliazh...@gmail.com> wrote:
>>
>>> Yes, it's definitely much quicker than a few months ago.
>>> I agree with Yi on the redirecting thing.
>>>
>>> Thanks
>>>
>>> Wenli
>>>
>>>
>>> On Tue, Apr 21, 2020 at 11:12 AM Yi Shen <shenyi....@gmail.com> wrote:
>>>
>>>> It seems a lot faster now.
>>>>
>>>> Can we try redirecting www.echartsjs.com to echarts.apache.org, and keep
>>>> collecting developers' feedback about inaccessible of the website?
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Apr 16, 2020 at 4:11 PM Kevin A. McGrail <kmcgr...@apache.org>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Thu, Apr 16, 2020, 04:04 Ovilia <oviliazh...@gmail.com> wrote:
>>>>>
>>>>>> Hi Kevin,
>>>>>>
>>>>>> That's a good idea.
>>>>>>
>>>>>> We will test it again and find out the bottleneck with the updated
>>>> CDN
>>>>>> status.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Wenli
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 16, 2020 at 3:52 PM Kevin A. McGrail <
>>>> kmcgr...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> This month is a reporting month for echarts.  Let's try and get a
>>>> full
>>>>>>> status on the cdn and any other blockers to migrating to
>>>>>>> echarts.apache.org,
>>>>>>> please?
>>>>>>>
>>>>>>> On Wed, Apr 15, 2020, 22:53 Yi Shen <shenyi....@gmail.com> wrote:
>>>>>>>
>>>>>>>> Perhaps we can remove the videos when designing the new main
>>>> page for
>>>>>> the
>>>>>>>> 5.0 release. Ovilia has proposed this idea several times.
>>>>>>>>
>>>>>>>> On Thu, Apr 16, 2020 at 2:45 AM Kevin A. McGrail <
>>>>> kmcgr...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> The issue is significantly subpar access especially inside of
>>>> China
>>>>>>> that
>>>>>>>>> a CDN can help mitigate.
>>>>>>>>>
>>>>>>>>> On 4/15/2020 1:30 PM, Dave Fisher wrote:
>>>>>>>>>> Hi -
>>>>>>>>>>
>>>>>>>>>> In the last few months the Apache Infrastructure team has
>>>> moved a
>>>>>>> huge
>>>>>>>>> amount of traffic away from www.apache.org to
>>>> downloads.apache.org
>>>>> .
>>>>>> In
>>>>>>>>> light of this I think it might be a good idea to get back to
>>>> the
>>>>> long
>>>>>>>>> standing where the charts website is question.
>>>>>>>>>> Ideally it should be echarts.apache.org without needing a
>>>> CDN.
>>>>> Is
>>>>>>> the
>>>>>>>>> issue more the very large video on the main page which then
>>>>> requires
>>>>>>>>> certain byte range support on the server plus dealing with the
>>>>>> national
>>>>>>>>> firewalls, or is it the whole site. Can we find a compromise?
>>>>> Perhaps
>>>>>>> the
>>>>>>>>> video can be hosted in multiple places and have the page select
>>>>> which
>>>>>>> in
>>>>>>>> JS
>>>>>>>>> depending on where the user is?
>>>>>>>>>> Just some thoughts.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Dave
>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-h...@echarts.apache.org
>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Kevin A. McGrail
>>>>>>>>> kmcgr...@apache.org
>>>>>>>>>
>>>>>>>>> Member, Apache Software Foundation
>>>>>>>>> Chair Emeritus Apache SpamAssassin Project
>>>>>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-h...@echarts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>> --
>>>>>>>> Yi Shen
>>>>>>>> Apache ECharts(incubating) PPMC
>>>>>>>>
>>>>
>>>> --
>>>> Yi Shen
>>>> Apache ECharts(incubating) PPMC
>>>>
-- 
Kevin A. McGrail
kmcgr...@apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
For additional commands, e-mail: dev-h...@echarts.apache.org

Reply via email to