[PR] SLING-13246 allow a Content-Type response header with a charset [sling-org-apache-sling-starter]

["enapps-enorman (via GitHub)" <gi...@apache.org>]

enapps-enorman opened a new pull request, #641:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/641

   Update SmokeIT to allow a Content-Type response header with a charset
   
   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.
   
   `SmokeIT.ensureRepositoryIsStarted:201 Content-Type header Expected: "text/xml" but: was "text/xml;charset=utf-8"`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] SLING-13246 allow a Content-Type response header with a charset [sling-org-apache-sling-starter]

["enapps-enorman (via GitHub)" <gi...@apache.org>]

enapps-enorman merged PR #641:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/641


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org