ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anita Gnanamalar Jebaraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18871) HTTP responses needs to have the character encoding specified in the content type header
Date Tue, 15 Nov 2016 00:24:58 GMT

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

Anita Gnanamalar Jebaraj updated AMBARI-18871:
----------------------------------------------
    Attachment: AMBARI-18871-updated.patch

Updated the test cases

> HTTP responses needs to have the character encoding specified in the content type header
> ----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18871
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18871
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Anita Gnanamalar Jebaraj
>            Assignee: Anita Gnanamalar Jebaraj
>             Fix For: trunk
>
>         Attachments: AMBARI-18871-updated.patch, AMBARI-18871.patch
>
>
> The charset information(UTF-8) can be added to all the response headers to harden the
security for the client. When the charset information is not specified the web browser may
choose a different encoding by guessing which encoding is actually being used by the web page.

> This specific issue is mentioned in the section 3.1.1.5 of RFC7231



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message