Skip to content

Enhance Traffic Inspector: Request Capture, History, and Structuring #2

@dpkrn

Description

@dpkrn

Summary

Improve the traffic inspector to provide more granular inspection and manipulation of HTTP request/response flows.

Proposed Enhancements

  • Capture Request Configuration Like Postman

    • Capture and expose every request's configuration items independently:
      • Parameters
      • Authorization
      • Body
      • Response
      • Headers
    • Allow modification of each part before forwarding (similar to Postman request editor).
  • Request History & Replay Enhancement

    • Improve the history mechanism to store and track each request, with user consent for history capture.
    • Allow users to easily replay previous requests from the history.
  • Request/Response Body Structuring

    • Add better structuring for both request and response bodies, making them easily viewable and editable.

Motivation

Improving the inspector with these features will provide developers with better control and visibility over their tunnelled traffic, making debugging and development workflows more productive and user-friendly.

Acceptance Criteria

  • Each part of a request can be reviewed and edited independently before sending (param, auth, body, response, header).
  • History of requests can be stored and replayed, with controls for user consent.
  • Request and response bodies are displayed in a structured, easily readable format.

Repo: dpkrn/gotunnel

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions