From b3f67a16094168cc334f5da93a86f09476e01601 Mon Sep 17 00:00:00 2001
From: xXx-caillou-xXx
Date: Thu, 30 Aug 2018 15:02:22 +0200
Subject: Change how we're handling invalid configurations

Since our configuration format is a bit more complex than php's one,
we have a `sp.allow_broken_configuration` parameter (`false` by default),
that you can set to `true` if you want PHP to carry on if your Snuffleupagus'
configuration contains syntax errors. You'll still get a big scary message in
your logs of course. We do **not** recommend to use it of course, but sometimes
it might be useful to be able to "debug in production" without breaking your
website.---
 src/tests/upload_validation.phpt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'src/tests/upload_validation.phpt')

diff --git a/src/tests/upload_validation.phpt b/src/tests/upload_validation.phpt
index bdcbc60..1daebb6 100644
--- a/src/tests/upload_validation.phpt
+++ b/src/tests/upload_validation.phpt
@@ -13,5 +13,6 @@ Content-Disposition: form-data; name="test"; filename="test.php"
 echo 1;
 ?>
 --EXPECTF--
-1
-Fatal error: [snuffleupagus][config] A rule can't be enabled and disabled on line 1 in Unknown on line 0
\ No newline at end of file
+Fatal error: [snuffleupagus][config] Invalid configuration file in Unknown on line 0
+
+Fatal error: [snuffleupagus][config] A rule can't be enabled and disabled on line 1 in Unknown on line 0
-- 
cgit v1.3