You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by ol...@apache.org on 2025/06/01 14:15:28 UTC

(httpcomponents-website) branch master updated (1b12393 -> dc1b64d)

This is an automated email from the ASF dual-hosted git repository.

olegk pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/httpcomponents-website.git


 discard 1b12393  Formatting (no content changes)
     new dc1b64d  Formatting (no content changes)

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (1b12393)
            \
             N -- N -- N   refs/heads/master (dc1b64d)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 src/site/markdown/security.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)


(httpcomponents-website) 01/01: Formatting (no content changes)

Posted by ol...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

olegk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/httpcomponents-website.git

commit dc1b64d839e53f60a2d815202401395a0b52d1a6
Author: Oleg Kalnichevski <ol...@apache.org>
AuthorDate: Sun Jun 1 11:53:09 2025 +0200

    Formatting (no content changes)
---
 src/site/markdown/security.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/src/site/markdown/security.md b/src/site/markdown/security.md
index 3c7e813..3eb9e75 100644
--- a/src/site/markdown/security.md
+++ b/src/site/markdown/security.md
@@ -28,10 +28,14 @@ The Apache HttpComponents operates under the [Apache-wide security procedures](h
 HttpComponents Security Model
 -----------------------------
 
-The HttpComponents libraries are low-level libraries typically designed to work with input that is either trusted or validated/sanitized by the application using the library. It is unsafe to provide possibly malicious input to HttpComponents libraries unless otherwise specified.
-
-We consider calls to the HttpComponents API subject to the same caveat as the JDK, those calls will usually do what the caller asks. Whether it is "dangerous" depends on the (application) context. Therefore, don't report a behavior as a HttpComponents component's vulnerability if the same behavior would be considered legitimate for the JDK. We welcome suggestions for hardening the code base.
-
-For example, if your program adds an HTTP header to a request, you are responsible for the data you add to that header.
-On the other hand, the headers that are added and removed by HttpComponents are its responsibility.
+The HttpComponents libraries are low-level libraries typically designed to work with input that is either trusted or
+validated/sanitized by the application using the library. It is unsafe to provide possibly malicious input to
+HttpComponents libraries unless otherwise specified.
+
+We consider calls to the HttpComponents API subject to the same caveat as the JDK, those calls will usually do what the
+caller asks. Whether it is "dangerous" depends on the (application) context. Therefore, don't report a behavior as a
+HttpComponents component's vulnerability if the same behavior would be considered legitimate for the JDK. We welcome
+suggestions for hardening the code base. For example, if your program adds an HTTP header to a request, you are
+responsible for the data you add to that header. On the other hand, the headers that are added and removed by
+HttpComponents are its responsibility.