You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2026/09/09 22:29:06 UTC
(pekko-http) branch pjfanning-patch-2 created (now 486c14f9f)
This is an automated email from the ASF dual-hosted git repository.
pjfanning pushed a change to branch pjfanning-patch-2
in repository https://gitbox.apache.org/repos/asf/pekko-http.git
at 486c14f9f Fix typo in reference.conf comment
This branch includes the following new commits:
new 486c14f9f Fix typo in reference.conf comment
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org
(pekko-http) 01/01: Fix typo in reference.conf comment
Posted by fa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pjfanning pushed a commit to branch pjfanning-patch-2
in repository https://gitbox.apache.org/repos/asf/pekko-http.git
commit 486c14f9f7ee4990b93609a51aa92e2703ef3b32
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Wed Sep 9 23:29:00 2026 +0100
Fix typo in reference.conf comment
---
http/src/main/resources/reference.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/http/src/main/resources/reference.conf b/http/src/main/resources/reference.conf
index 7410f8afe..b3384f8fd 100644
--- a/http/src/main/resources/reference.conf
+++ b/http/src/main/resources/reference.conf
@@ -53,7 +53,7 @@ pekko.http {
# Maximum content length after applying a decoding directive. When the directive
# decompresses, for example, an entity compressed with gzip, the resulting stream can be much
- # larger than the max-content-length. Like with max-content-length, this is not necessarilly a
+ # larger than the max-content-length. Like with max-content-length, this is not necessarily a
# problem when consuming the entity in a streaming fashion, but does risk high memory use
# when the entity is made strict or marshalled into an in-memory object.
# This limit (like max-content-length) can be overridden on a case-by-case basis using the
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org