Skip to content

Conversation

@tugkanboz
Copy link

@tugkanboz tugkanboz commented Sep 30, 2025

Problem

HTTP Imposter detail pages (/imposters/{port}) only displayed generic titles like "http Imposter on port 5034". This made it difficult for users to immediately identify which service/API was running on that port.

Solution

Enhanced the imposter detail page to display the imposter's name field in the title when available, providing better service identification.

Results

  • With name: "E-Commerce API - http Imposter on port 5034"
  • Without name: "http Imposter on port 5034" (unchanged behavior)

Benefits

  1. Improved User Experience: Service identity is immediately clear
  2. Backward Compatibility: Existing imposters without names are unaffected

Test Examples

Named imposter

  {
    "name": "User Management API",
    "port": 3000,
    "protocol": "http"
  }

Result: "User Management API - http Imposter on port 3000"

Unnamed imposter (existing behavior)

  {
    "port": 4000,
    "protocol": "http"
  }

Result: "http Imposter on port 4000" (no change)

This enhancement is particularly valuable for teams running multiple imposters simultaneously!

Include request body in HTTP imposter logs when body is present.
This enhances debugging capabilities by showing the complete request data sent to mocked endpoints in the logs.
Include request body in HTTP imposter logs when body is present.
This enhances debugging capabilities by showing the complete request data sent to mocked endpoints in the logs.
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant