This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new a87e86dbd Updates stage by Jenkins
a87e86dbd is described below
commit a87e86dbd09a1d63a904efe6552e1152fcc5167b
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Jan 3 01:12:43 2024 +0000
Updates stage by Jenkins
---
content/security/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/security/index.html b/content/security/index.html
index 477442f7b..998d4b1cc 100644
--- a/content/security/index.html
+++ b/content/security/index.html
@@ -469,7 +469,7 @@ state.</p>
<h3 id="restricting-access-to-the-struts-context-actioncontext">Restricting
access to the Struts Context (ActionContext)</h3>
<p>The Struts ActionContext is a core construct of the Struts framework. It is
shared and manipulated throughout the
-codebase. From the ActionContext, it is possible to access application
parameters, the ‘OgnlValueStack’, the current
+codebase. From the ActionContext, it is possible to access application
parameters, the OgnlValueStack, the current
request/response/session, the servlet context, the Guice container, and a
number of other objects either directly or
indirectly via the directly exposed objects. The Struts ActionContext enables
powerful features and functionality, but
it also presents a major security risk if not properly secured.</p>
