Allow users override maxInMemoryFileSize in multipartFileUpload

Description

Contributor guide

Tech stack

scala

Domain

backendapi

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

ScalaFinagle basics

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

The issue requests adding a user configurable maxInMemoryFileSize parameter to the multipart file upload feature in Finch. The relevant code is in MultipartDecoder.scala at line 20 (https://github.com/twitter/finagle/blob/develop/finagle base http/src/main/scala/com/twitter/finagle/http/exp/MultipartDecoder.scala#L20), where a default value is currently hardcoded. The solution involves exposing this as an optional parameter in the multipartFileUpload API, allowing users to override it. There is a Gitter discussion (https://gitter.im/finagle/finch?at=5c6f1c2de5eeec0d9ba469f9) that motivated this request. No linked PRs or assignees exist, so the issue is open for contribution.