From 0379c63ef9459b7c1b1fb76eebe806e8fcd67f8a Mon Sep 17 00:00:00 2001 From: Mart Lubbers Date: Wed, 16 Nov 2016 13:04:04 +0100 Subject: [PATCH] Go to plural --- report/v9_data.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/report/v9_data.tex b/report/v9_data.tex index 0e4e2f5..5a38911 100644 --- a/report/v9_data.tex +++ b/report/v9_data.tex @@ -4,7 +4,7 @@ features. \begin{result} - The login and page/post editing/creation forms post back to the same page, thereby incentivising the browser to cache the form inputs as well. This is as opposed to the common post/redirect/get model (see \url{http://en.wikipedia.org/wiki/Post/Redirect/Get}). Also, the \code{Cache-Control} isn't explicitly used anywhere in the \CMS{} to aid the situation. In my test setup, the response does send \code{Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0}, but that'll be a default global Apache setting, I think. + The login and page/post editing/creation forms post back to the same page, thereby incentivising the browser to cache the form inputs as well. This is as opposed to the common post/redirect/get model (see \url{http://en.wikipedia.org/wiki/Post/Redirect/Get}). Also, the \code{Cache-Control} isn't explicitly used anywhere in the \CMS{} to aid the situation. In our test setup, the response does send \code{Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0}, but that'll be a default global Apache setting, we think. \end{result} \notapplicable{\item Verify that the list of sensitive data processed by the @@ -34,7 +34,7 @@ \end{verbatim} \begin{result} - Cache control header are never set by the \CMS{}. The fact that headers as these are indeed sent to the broswer in my test setup is probably due to default global Apache settings. + Cache control header are never set by the \CMS{}. The fact that headers as these are indeed sent to the broswer in our test setup is probably due to default global Apache settings. \end{result} \item\pass{} Verify that on the server, all cached or temporary copies @@ -55,7 +55,7 @@ variables, cookies and header values. \begin{result} - The \CMS{} by no means sends any larger amount of parameters than would be expected, seen as it is but a simple app and mostly lacks extra functionality often leading to this kind of excessive parameter transferring, so I count this as a pass. + The \CMS{} by no means sends any larger amount of parameters than would be expected, seen as it is but a simple app and mostly lacks extra functionality often leading to this kind of excessive parameter transferring, so we count this as a pass. \end{result} \notapplicable{\item Verify the application has the ability to detect and alert -- 2.20.1