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 <[email protected]> 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: [email protected] For additional commands, e-mail: [email protected]
