Headers (Auto & Custom)
The Headers editor is used in two places: inside the request panel (for the headers the mock expects) and inside the response panel (for the headers the mock sends back). Both sides use the same editor, so the layout is the same on request and response. The only difference is a single extra checkbox on the request side.
Auto-Generated Content-Type
The top of the Headers tab holds an Auto-generatedsection with a single row — the Content-Typeheader. This row is not part of the custom headers list; Tigrister keeps it separate and fills its value automatically from the body type of the endpoint:
- •JSON body → application/json
- •XML body → application/xml
- •Text body → text/plain
- •Form data → multipart/form-data
- •URL-encoded → application/x-www-form-urlencoded
- •None: no auto row is shown, because there is nothing to type.
The auto row has its own enable checkbox, so you can temporarily turn it off without deleting anything. If you also add a custom header whose key is Content-Type, Tigrister hides that duplicate from the custom list so the UI only ever shows one Content-Type row at a time.
Custom Headers
Below the auto section sits the Custom Headerstable. It is a standard key-value editor:
- •Enable checkbox — disabled rows are dimmed and ignored.
- •Key and Value text fields.
- •Delete button on the right of each row.
- •Add Header button under the table adds a fresh empty row.
Match Headers (Request Side Only)
On the request side, the Headers tab has one extra checkbox at the very top: Match Headers. Turning it on marks these headers as part of the incoming-request contract for the endpoint — a signal that the mock should pay attention to the headers when deciding whether this endpoint is the right one. Response-side headers never have this checkbox, because response headers are what the mock sends, not what it checks.