From 0c074e4348ff101ba24a59f3155afdafa8d947db Mon Sep 17 00:00:00 2001
From: Andrew Ruthven <puck@catalyst.net.nz>
Date: Thu, 29 Nov 2018 13:40:12 +1300
Subject: [PATCH] Explicitly set the Charset to use, and look for the usual
 format.

In the GitLab CI environment, the command:

@header("Content-Type: text/plain");

Generates the Content-Type line of:

Content-Type: text/plain; charset=UTF-8

But on my workstation it generates this:

Content-Type: text/plain;charset=UTF-8

By adding that charset to our call to @header, we receive a
predictable result.
---
 testing/test-RRULE-v2.php                               | 2 +-
 testing/tests/regression-suite/0831-Spec-RRULE-1.result | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/testing/test-RRULE-v2.php b/testing/test-RRULE-v2.php
index 8a2c7bd5..5f864061 100755
--- a/testing/test-RRULE-v2.php
+++ b/testing/test-RRULE-v2.php
@@ -12,7 +12,7 @@ $c->dbg = array();
 require_once("RRule.php");
 require_once('AwlQuery.php');
 
-@header("Content-Type: text/plain");
+@header("Content-Type: text/plain; charset=UTF-8");
 
 echo <<<EOTXT
 Testing the RRule v2 Library
diff --git a/testing/tests/regression-suite/0831-Spec-RRULE-1.result b/testing/tests/regression-suite/0831-Spec-RRULE-1.result
index f80a5744..9c1cbded 100644
--- a/testing/tests/regression-suite/0831-Spec-RRULE-1.result
+++ b/testing/tests/regression-suite/0831-Spec-RRULE-1.result
@@ -3,7 +3,7 @@ Date: Dow, 01 Jan 2000 00:00:00 GMT
 DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
 DAV: extended-mkcol, bind, addressbook, calendar-auto-schedule, calendar-proxy
 Content-Length: 7623
-Content-Type: text/plain;charset=UTF-8
+Content-Type: text/plain; charset=UTF-8
 
 #!/usr/bin/php
 Testing the RRule v2 Library