[ 
https://issues.apache.org/jira/browse/HADOOP-16448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaspar Tint updated HADOOP-16448:
---------------------------------
    Description: 
When visiting the [Hadoop 
website|https://hadoop.apache.org/docs/r3.2.0/index.html] with the latest 
Firefox browser (v 68.0.1) it appears that the website cannot be reached 
through secure means by default.

The culprit seems to be the fact that the two header images presented on the 
page are loaded in via *HTTP*
 !Screen Shot 2019-07-23 at 9.37.54 AM.png!.

These images are located in the respective locations:
http://hadoop.apache.org/images/hadoop-logo.jpg
http://www.apache.org/images/asf_logo_wide.png

These images can be reached also from the following locations:
https://hadoop.apache.org/images/hadoop-logo.jpg
https://www.apache.org/images/asf_logo_wide.png

As one can see, a fix could be made to use a more safe way of including in the 
two header pictures to the page.

I feel like I am in danger when reading the Hadoop documentation from the 
official Hadoop webpage in a non secure way. Thus I felt the need to open this 
ticket and raise the issue in order to have a future where everyone can learn 
from Hadoop documentation in a safe and secure way.

  was:
When visiting the Hadoop website with the latest Firefox browser (v 68.0.1) it 
appears that the website cannot be reached through secure means by default.

The culprit seems to be the fact that the two header images presented on the 
page are loaded in via *HTTP*
 !Screen Shot 2019-07-23 at 9.37.54 AM.png!.

These images are located in the respective locations:
http://hadoop.apache.org/images/hadoop-logo.jpg
http://www.apache.org/images/asf_logo_wide.png

These images can be reached also from the following locations:
https://hadoop.apache.org/images/hadoop-logo.jpg
https://www.apache.org/images/asf_logo_wide.png

As one can see, a fix could be made to use a more safe way of including in the 
two header pictures to the page.

I feel like I am in danger when reading the Hadoop documentation from the 
official Hadoop webpage in a non secure way. Thus I felt the need to open this 
ticket and raise the issue in order to have a future where everyone can learn 
from Hadoop documentation in a safe and secure way.


> Connection to Hadoop homepage is not secure
> -------------------------------------------
>
>                 Key: HADOOP-16448
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16448
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 3.1.0, 3.2.0, 2.7.7
>            Reporter: Kaspar Tint
>            Priority: Major
>         Attachments: Screen Shot 2019-07-23 at 9.37.54 AM.png
>
>
> When visiting the [Hadoop 
> website|https://hadoop.apache.org/docs/r3.2.0/index.html] with the latest 
> Firefox browser (v 68.0.1) it appears that the website cannot be reached 
> through secure means by default.
> The culprit seems to be the fact that the two header images presented on the 
> page are loaded in via *HTTP*
>  !Screen Shot 2019-07-23 at 9.37.54 AM.png!.
> These images are located in the respective locations:
> http://hadoop.apache.org/images/hadoop-logo.jpg
> http://www.apache.org/images/asf_logo_wide.png
> These images can be reached also from the following locations:
> https://hadoop.apache.org/images/hadoop-logo.jpg
> https://www.apache.org/images/asf_logo_wide.png
> As one can see, a fix could be made to use a more safe way of including in 
> the two header pictures to the page.
> I feel like I am in danger when reading the Hadoop documentation from the 
> official Hadoop webpage in a non secure way. Thus I felt the need to open 
> this ticket and raise the issue in order to have a future where everyone can 
> learn from Hadoop documentation in a safe and secure way.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to