| On | Key | Value | Remove |
|---|---|---|---|
|
|
| On | Header | Value | Remove |
|---|---|---|---|
|
|
{{ formattedBody }}
| Header | Value | Copy |
|---|---|---|
| {{ h.key }} | {{ h.value }} | |
| No headers returned. | ||
{{ rawRequest }}
{{ JSON.stringify({ url: responseURL, status: responseStatus, statusText: responseStatusText, ok: responseOk, type: responseType, sizeBytes: responseSizeBytes, elapsedMs }, null, 2) }}
| Name | Method | URL | Actions |
|---|---|---|---|
| {{ entry.name }} | {{ entry.method }} | {{ entry.url }} |
|
| No saved requests yet. | |||
Web request testing is the practice of sending a request to a service address and reading the reply. It helps you confirm what an endpoint accepts and returns in everyday terms. Many people look for a simple way to test web service endpoints without setting up scripts or extra software.
Enter a target address and pick a request method. Add any query pairs or custom headers and include a message body when updates are needed, then send. You will see the returned status text plus any response content and key headers as well as the total time, and you can paste a command string to auto fill fields for quick setup.
For example, request a list of users from a demo address with a small limit and expect a short set of names. If you update a record you might send a small body and see confirmation in the reply. Network timing can swing between runs and short tests can show surprising jumps or streaks.
Get clearer results by naming requests so you can compare runs later and by keeping secrets out of saved entries. Use pretty print when a reply is structured and toggle parameters to compare scenarios. When a service moves you elsewhere try a strict redirect setting to see what happens step by step.
Hypertext Transfer Protocol (HTTP) requests are actions sent to a Uniform Resource Locator (URL) with a method, optional headers, and an optional body. The app composes a final address from the base address and any enabled query key–value pairs, applies headers, and includes a body only for non‑GET and non‑HEAD methods.
Bodies that look like JSON are detected and pretty printed, and a Content‑Type header of application/json is added when none is set. Authentication can attach either a Basic header built from username and password or a Bearer token. A timeout can abort a request, and redirects can be followed, blocked with an error, or left manual.
Status, response type, size in bytes, and elapsed time in milliseconds are presented alongside the body. When the response type is HTML, a safe preview is shown in a frame. If the payload is binary or cannot be decoded as text, a short note with the byte count is shown instead of raw bytes.
| Field | Type | Min | Max | Step/Pattern | Error Text | Placeholder |
|---|---|---|---|---|---|---|
| Name | Text | — | — | — | — | Untitled request |
| Method | Select | — | — | GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS | — | — |
| URL | Text | — | — | Accepts full addresses; query pairs can auto‑populate | No URL provided. | https://api.example.com/users?limit=10 |
| Timeout (ms) | Number | 0 | — | Step 100 | Aborted on timeout | 9000 |
| Redirects | Select | — | — | follow, error, manual | — | — |
| Auth | Select | — | — | None, Basic, Bearer | — | — |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Address | Full address strings with optional query pairs | Echoed in request preview | As typed | None |
| Headers | Key–value text; default Accept: application/json | Table and CSV copy/download | UTF‑8 text | None |
| Body | Arbitrary text; JSON detected best‑effort | Raw, highlighted JSON, or binary note | Charset from response; fallback UTF‑8 | None |
| Auth | Basic user:pass; Bearer token | Authorization header | Base64 for Basic credentials | Exact |
| Timing & size | — | Elapsed ms and byte count | Integer milliseconds; integer bytes | No rounding beyond integers |
Work is linear in response size. Responses are buffered to measure bytes, then decoded for display. For non‑text types the decoder samples a small portion to decide whether text should be shown or replaced by a binary note.
A raw request preview and a response meta block provide a reproducible trace. Identical inputs yield the same request structure, although network timing and upstream behavior can vary between runs.
Goal: Read a small list of users.
If the type is JSON it is highlighted and can be copied or downloaded.
Use web request testing to verify a service address and interpret its reply clearly.
Example: Method GET, address with limit=3, header Accept: application/json.
You now have a concise view of what the service returned and how long it took.
Saved requests live in local storage on your device. Sending a request contacts the target service directly from your browser, so the API’s CORS policy determines whether it succeeds. No server‑side storage is used for saved items.
Clear saved entries if they contain secrets.Elapsed time is measured on the device from request start to response processing. It includes network transfer and decoding, so values vary by connection and payload size.
Time is shown in milliseconds and size in bytes. Text is decoded using the response charset when present, otherwise UTF‑8. Structured replies are detected best‑effort for highlighting.
You can edit and manage saved requests without a connection. Sending requests needs network access and will fail when offline or when a service blocks cross‑origin calls.
No pricing or licensing terms are declared in the package. Use it as provided and review your organization’s policy before storing credentials locally.
This utility sends web requests and inspects replies. It does not parse certificate requests. Use a certificate‑specific validator to check CSR structure and signatures.
Only responses labeled as HTML are rendered in the preview. Other types show text or a binary note. Switch to the Body tab to view raw content.