From 527606a93b29c67d1563d11cfaff5a43c9514676 Mon Sep 17 00:00:00 2001 From: Gus Brodman Date: Tue, 11 Aug 2026 15:29:33 -0400 Subject: [PATCH] Lower maximum message length bytes in EPP server We don't need to accept anything anywhere close to this big, and we shouldn't risk large messages causing OOMs D.1 number 2 b/535251458 --- .../java/google/registry/proxy/config/default-config.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/proxy/src/main/java/google/registry/proxy/config/default-config.yaml b/proxy/src/main/java/google/registry/proxy/config/default-config.yaml index 5205fa074df..e0e1d305b59 100644 --- a/proxy/src/main/java/google/registry/proxy/config/default-config.yaml +++ b/proxy/src/main/java/google/registry/proxy/config/default-config.yaml @@ -61,13 +61,11 @@ epp: # # The first 4 bytes in a message is the total length of message, in bytes. # - # We accept a message up to 1 GB, which should be plentiful, if not over the - # top. In fact, we should probably limit this to a more reasonable number, as - # a 1 GB message will likely cause the proxy to go out of memory. + # We accept a message up to 10 MB, which should be plentiful. # # See also: RFC 5734 4 Data Unit Format # (https://tools.ietf.org/html/rfc5734#section-4). - maxMessageLengthBytes: 1073741824 + maxMessageLengthBytes: 10485760 # Length of the header field in bytes. #