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

Eric Norman updated SLING-13246:
--------------------------------
    Description: 
The latest versions of jetty are appending the charset to the Content-Type 
header of the response.

The result is the following assertion failing in the smote test.  Fix by 
adjusting the value matching to allow an optional charset suffix.
{code:java}
SmokeIT.ensureRepositoryIsStarted:201 Content-Type header Expected: "text/xml" 
but: was "text/xml;charset=utf-8"{code}
 

  was:
The latest versions of jetty are appending the charset to the Content-Type 
header of the response.

The result is the following assertion failing in the smote test.  Fix by 
adjusting the value matching to allow an optional charset suffix.

{{}}
{code:java}
SmokeIT.ensureRepositoryIsStarted:201 Content-Type header Expected: "text/xml" 
but: was "text/xml;charset=utf-8"{code}
{{}}


> Update SmokeIT to allow a Content-Type response header with a charset
> ---------------------------------------------------------------------
>
>                 Key: SLING-13246
>                 URL: https://issues.apache.org/jira/browse/SLING-13246
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: Starter 15
>
>
> The latest versions of jetty are appending the charset to the Content-Type 
> header of the response.
> The result is the following assertion failing in the smote test.  Fix by 
> adjusting the value matching to allow an optional charset suffix.
> {code:java}
> SmokeIT.ensureRepositoryIsStarted:201 Content-Type header Expected: 
> "text/xml" but: was "text/xml;charset=utf-8"{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to