Make the history item truncation limit configurable - #112
Open
redteam10it wants to merge 1 commit into
Open
Conversation
Recorded-traffic tools (proxy/WebSocket history, Organizer) cap each item at a hard-coded 5000 characters of serialized JSON. Because the request is serialized before the response, items with large requests can consume the whole budget and drop the response entirely, which is usually the most useful part. This addresses PortSwigger#100. - Add a persisted historyItemMaxChars setting (default 5000, preserving current behaviour). A value of 0 or less disables truncation. - truncateIfNeeded now takes the limit from config instead of a literal. - Expose the setting in the MCP tab's Advanced Options. Unlike host/port it is a live setting: it does not require a reinstall and stays editable while the server is running.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The recorded-traffic tools (proxy/WebSocket history and Organizer) cap each item at a hard-coded 5000 characters of serialized JSON. Since the request is serialized before the response, an item with a large request (e.g. a big cookie header) can use up the whole budget and the response gets dropped entirely, which is usually the part you want.
historyItemMaxCharssetting (default 5000, so current behaviour is unchanged). A value of 0 or less disables truncation.truncateIfNeededreads the limit from config instead of a literal.Closes #100.
Test plan
./gradlew testpasses