@jaredwray/mockhttp
v1.4.0
Published
Mock Http - Easy way to mock http with httpbin replacement
Downloads
176
Maintainers
Readme
A simple HTTP server that can be used to mock HTTP responses for testing purposes. Inspired by httpbin and built using nodejs and fastify with the idea of running it via https://mockhttp.org, via docker jaredwray/mockhttp, or nodejs npm install jaredwray/mockhttp.
Features
- All the features of httpbin
- Taps - Inject custom responses for testing and develepment
@fastify/helmetbuilt in by default- Built with
nodejs,typescript, andfastify - Deploy via
dockerornodejs - Global deployment via mockhttp.org (free service)
- Better API documentation and examples
- Auto detect the port that is not in use
- Maintained and updated regularly!
Table of Contents
- Deploy via Docker
- Deploy via Docker Compose
- Deploy via NodeJS
- HTTPS Support
- Response Injection (Tap Feature)
- Rate Limiting
- Logging
- API Reference
- About mockhttp.org
- Contributing
- License
Deploy via Docker
docker run -d -p 3000:3000 jaredwray/mockhttpDeploy via Docker Compose
services:
mockhttp:
image: jaredwray/mockhttp:latest
ports:
- "3000:3000"If you want to run it on a different port, just change the 3000 to whatever port you want and add in the environment variable PORT to the environment.
services:
mockhttp:
image: jaredwray/mockhttp:latest
ports:
- "3001:3001"
environment:
- PORT=3001You can see an example of this in the docker-compose.yaml file.
Deploy via NodeJS
npm install @jaredwray/mockhttp --savethen run mockhttp in your code.
import { MockHttp } from '@jaredwray/mockhttp';
const mock = new MockHttp();
await mock.start(); // start the server
const response = await fetch('http://localhost:3000/get');
console.log(response);
await mock.close(); // stop the serverHTTPS Support
MockHttp supports HTTPS with auto-generated self-signed certificates or your own custom certificates. No external dependencies are required — certificate generation uses only Node.js built-in crypto.
Auto-Generated Certificate
The simplest way to enable HTTPS is to pass https: true. A self-signed certificate for localhost is generated automatically:
import { MockHttp } from '@jaredwray/mockhttp';
const mock = new MockHttp({ https: true });
await mock.start();
console.log(mock.isHttps); // true
// Use Fastify's built-in inject() for testing (no TLS setup needed)
const response = await mock.server.inject({ method: 'GET', url: '/get' });
console.log(response.statusCode); // 200
await mock.close();Note: Self-signed certificates are not trusted by default. When making real HTTPS requests (e.g. with
fetch), setNODE_TLS_REJECT_UNAUTHORIZED=0in your test environment or use a custom HTTPS agent.
Custom Certificate Options
You can customize the auto-generated certificate by passing certificateOptions:
const mock = new MockHttp({
https: {
certificateOptions: {
commonName: 'my-test-server',
validityDays: 30,
keySize: 4096,
altNames: [
{ type: 'dns', value: 'example.local' },
{ type: 'dns', value: '*.example.local' },
{ type: 'ip', value: '192.168.1.100' },
],
},
},
});
await mock.start();
// Make requests...
await mock.close();Provide Your Own Certificate
You can supply your own PEM-encoded certificate and key, either as strings or file paths:
// Using PEM strings
const mock = new MockHttp({
https: {
cert: '-----BEGIN CERTIFICATE-----\n...',
key: '-----BEGIN PRIVATE KEY-----\n...',
},
});
await mock.start();
// Make requests...
await mock.close();// Using file paths
const mock = new MockHttp({
https: {
cert: '/path/to/cert.pem',
key: '/path/to/key.pem',
},
});
await mock.start();
// Make requests...
await mock.close();Standalone Certificate Generation
You can also generate certificates independently using the exported utility functions:
import { generateCertificate, generateCertificateFiles } from '@jaredwray/mockhttp';
// Generate in-memory PEM strings
const { cert, key } = generateCertificate({
commonName: 'my-app',
validityDays: 90,
});
// Generate and write to disk
const result = await generateCertificateFiles({
certPath: './certs/cert.pem',
keyPath: './certs/key.pem',
commonName: 'my-app',
});HTTPS Options Reference
| Option | Type | Default | Description |
|--------|------|---------|-------------|
| cert | string | — | PEM-encoded certificate string or file path |
| key | string | — | PEM-encoded private key string or file path |
| autoGenerate | boolean | true | Auto-generate a self-signed certificate when cert/key are not provided |
| certificateOptions | CertificateOptions | — | Options for the auto-generated certificate |
Certificate Options
| Option | Type | Default | Description |
|--------|------|---------|-------------|
| commonName | string | 'localhost' | Certificate subject Common Name (CN) |
| altNames | Array<{ type, value }> | [dns:localhost, ip:127.0.0.1, ip:::1] | Subject Alternative Names with type 'dns' or 'ip' |
| validityDays | number | 365 | Certificate validity period in days |
| keySize | number | 2048 | RSA key size in bits |
Response Injection (Tap Feature)
The injection/tap feature allows you to "tap into" the request flow and inject custom responses for specific requests. This is particularly useful for:
- Offline testing - Mock external API responses without network access
- Testing edge cases - Simulate errors, timeouts, or specific response scenarios
- Development - Work on your application without depending on external services
What is a "Tap"?
A "tap" is a reference to an injected response, similar to "wiretapping" - you're intercepting requests and returning predefined responses. Each tap can be removed when you're done with it, restoring normal server behavior.
Basic Usage
import { mockhttp } from '@jaredwray/mockhttp';
const mock = new mockhttp();
await mock.start();
// Inject a simple response
const tap = mock.taps.inject(
{
response: "Hello, World!",
statusCode: 200,
headers: { "Content-Type": "text/plain" }
},
{
url: "/api/greeting",
method: "GET"
}
);
// Make requests - they will get the injected response
const response = await fetch('http://localhost:3000/api/greeting');
console.log(await response.text()); // "Hello, World!"
// Remove the injection when done
mock.taps.removeInjection(tap);
await mock.close();Advanced Examples
Inject JSON Response
const tap = mock.taps.inject(
{
response: { message: "Success", data: { id: 123 } },
statusCode: 200
},
{ url: "/api/users/123" }
);Wildcard URL Matching
// Match all requests under /api/
const tap = mock.taps.inject(
{
response: "API is mocked",
statusCode: 503
},
{ url: "/api/*" }
);Multiple Injections
const tap1 = mock.taps.inject(
{ response: "Users data" },
{ url: "/api/users" }
);
const tap2 = mock.taps.inject(
{ response: "Posts data" },
{ url: "/api/posts" }
);
// View all active injections
console.log(mock.taps.injections); // Map of all active taps
// Remove specific injections
mock.taps.removeInjection(tap1);
mock.taps.removeInjection(tap2);Match by HTTP Method
// Only intercept POST requests
const tap = mock.taps.inject(
{ response: "Created", statusCode: 201 },
{ url: "/api/users", method: "POST" }
);Match by Headers
const tap = mock.taps.inject(
{ response: "Authenticated response" },
{
url: "/api/secure",
headers: {
"authorization": "Bearer token123"
}
}
);Catch-All Injection
// Match ALL requests (no matcher specified)
const tap = mock.taps.inject({
response: "Server is in maintenance mode",
statusCode: 503
});Dynamic Function Response
You can provide a function that dynamically generates the response based on the incoming request:
// Function response with access to the request object
const tap = mock.taps.inject(
(request) => {
return {
response: {
message: `You requested ${request.url}`,
method: request.method,
timestamp: new Date().toISOString()
},
statusCode: 200,
headers: {
"X-Request-Path": request.url
}
};
},
{ url: "/api/*" }
);// Conditional responses based on request
const tap = mock.taps.inject((request) => {
// Return error for URLs containing 'error'
if (request.url.includes('error')) {
return {
response: { error: "Something went wrong" },
statusCode: 500
};
}
// Return success for everything else
return {
response: { status: "success" },
statusCode: 200
};
});// Dynamic headers based on request
const tap = mock.taps.inject(
(request) => ({
response: "OK",
statusCode: 200,
headers: {
"X-Original-Method": request.method,
"X-Original-URL": request.url,
"X-Original-Host": request.hostname
}
}),
{ url: "/api/mirror" }
);Rate Limiting
MockHttp supports rate limiting using @fastify/rate-limit. Rate limiting is enabled by default at 1000 requests per minute with localhost (127.0.0.1 and ::1) excluded from rate limiting.
Default Rate Limiting
By default, MockHttp applies the following rate limit:
- 1000 requests per minute per IP address
- Localhost is excluded - requests from 127.0.0.1 and ::1 bypass rate limiting (ideal for local development and testing)
import { MockHttp } from '@jaredwray/mockhttp';
const mock = new MockHttp();
await mock.start();
// Rate limiting is active (1000 req/min) except for localhostCustomizing Rate Limiting
To customize rate limiting, pass a rateLimit configuration object when creating your MockHttp instance:
import { MockHttp } from '@jaredwray/mockhttp';
const mock = new MockHttp({
rateLimit: {
max: 100, // Maximum 100 requests
timeWindow: '1 minute' // Per 1 minute window
}
});
await mock.start();Common Configuration Options
The rateLimit option accepts all @fastify/rate-limit options:
Basic Rate Limiting
// Limit to 50 requests per minute
const mock = new MockHttp({
rateLimit: {
max: 50,
timeWindow: '1 minute'
}
});Stricter Limits with Custom Error Response
const mock = new MockHttp({
rateLimit: {
max: 30,
timeWindow: 60000, // 1 minute in milliseconds
errorResponseBuilder: (req, context) => ({
statusCode: 429,
error: 'Too Many Requests',
message: `Rate limit exceeded. Try again in ${context.after}`
})
}
});Allow List (Exclude Specific IPs)
const mock = new MockHttp({
rateLimit: {
max: 100,
timeWindow: '1 minute',
allowList: ['127.0.0.1', '192.168.1.100'] // These IPs bypass rate limiting
}
});Custom Key Generator (Rate Limit by Header)
const mock = new MockHttp({
rateLimit: {
max: 100,
timeWindow: '1 minute',
keyGenerator: (request) => {
// Rate limit by API key instead of IP
return request.headers['x-api-key'] || request.ip;
}
}
});Advanced Configuration
const mock = new MockHttp({
rateLimit: {
global: true, // Apply to all routes
max: 100, // Max requests
timeWindow: '1 minute', // Time window
cache: 10000, // Cache size for tracking clients
skipOnError: false, // Don't skip on storage errors
ban: 10, // Ban after 10 rate limit violations
continueExceeding: false, // Don't reset window on each request
enableDraftSpec: true, // Use IETF draft spec headers
addHeaders: { // Customize rate limit headers
'x-ratelimit-limit': true,
'x-ratelimit-remaining': true,
'x-ratelimit-reset': true
}
}
});Disabling Rate Limiting
To disable rate limiting completely, set the rateLimit option to false:
const mock = new MockHttp({
rateLimit: false // Completely disable rate limiting
});
await mock.start();
// No rate limiting is applied to any requestsNote: To change rate limiting settings after the server has started, you must restart the server:
const mock = new MockHttp();
await mock.start(); // Starts with default rate limiting
// To change or disable rate limiting:
await mock.close();
mock.rateLimit = undefined; // or set new options
await mock.start(); // Restarts with new settingsAvailable Options
| Option | Type | Default | Description |
|--------|------|---------|-------------|
| max | number | function | 1000 | Maximum requests per time window |
| timeWindow | number | string | 60000 | Duration of rate limit window (milliseconds or string like '1 minute') |
| cache | number | 5000 | LRU cache size for tracking clients |
| allowList | array | function | [] | IPs or function to exclude from rate limiting |
| keyGenerator | function | IP-based | Function to generate unique client identifier |
| errorResponseBuilder | function | Default 429 | Custom error response function |
| skipOnError | boolean | false | Skip rate limiting if storage errors occur |
| ban | number | -1 | Ban client after N violations (disabled by default) |
| continueExceeding | boolean | false | Renew time window on each request while limited |
| enableDraftSpec | boolean | false | Use IETF draft specification headers |
For the complete list of options, see the @fastify/rate-limit documentation.
Logging
MockHttp uses Pino for logging via Fastify's built-in logger. Logging is enabled by default but can be disabled when needed.
Disabling Logging
import { MockHttp } from '@jaredwray/mockhttp';
const mock = new MockHttp({ logging: false });
await mock.start();
// Server runs silently without any log outputYou can also disable logging via the LOGGING environment variable:
LOGGING=false node your-app.jsAPI Reference
MockHttp Class
Constructor
new MockHttp(options?)Parameters:
options?(MockHttpOptions):port?: number - The port to listen on (default: 3000)host?: string - The host to listen on (default: '0.0.0.0')autoDetectPort?: boolean - Auto-detect next available port if in use (default: true)helmet?: boolean - Use Helmet for security headers (default: true)apiDocs?: boolean - Enable Swagger API documentation (default: true)rateLimit?: RateLimitPluginOptions - Configure rate limiting (default: 1000 req/min, localhost excluded)logging?: boolean - Enable logging (default: true)httpBin?: HttpBinOptions - Configure which httpbin routes to enablehttpMethods?: boolean - Enable HTTP method routes (default: true)redirects?: boolean - Enable redirect routes (default: true)requestInspection?: boolean - Enable request inspection routes (default: true)responseInspection?: boolean - Enable response inspection routes (default: true)statusCodes?: boolean - Enable status code routes (default: true)responseFormats?: boolean - Enable response format routes (default: true)cookies?: boolean - Enable cookie routes (default: true)anything?: boolean - Enable anything routes (default: true)auth?: boolean - Enable authentication routes (default: true)images?: boolean - Enable image routes (default: true)
https?: boolean | HttpsOptions - Enable HTTPS with auto-generated or custom certificates (default: undefined/disabled)hookOptions?: HookifiedOptions - Hookified options
Properties
port: number - Get/set the server porthost: string - Get/set the server hostautoDetectPort: boolean - Get/set auto-detect port behaviorhelmet: boolean - Get/set Helmet security headersapiDocs: boolean - Get/set API documentationlogging: boolean - Get/set logging enabled staterateLimit: RateLimitPluginOptions | undefined - Get/set rate limiting optionshttpBin: HttpBinOptions - Get/set httpbin route optionshttps: HttpsOptions | undefined - Get/set HTTPS configurationisHttps: boolean - Whether the server is running with HTTPSserver: FastifyInstance - Get/set the Fastify server instancetaps: TapManager - Get/set the TapManager instance
Methods
async start()
Start the Fastify server. If already running, it will be closed and restarted.
async close()
Stop the Fastify server.
async detectPort()
Detect the next available port.
Returns: number - The available port
async registerApiDocs(fastifyInstance?)
Register Swagger API documentation routes.
async registerHttpMethods(fastifyInstance?)
Register HTTP method routes (GET, POST, PUT, PATCH, DELETE).
async registerStatusCodeRoutes(fastifyInstance?)
Register status code routes.
async registerRequestInspectionRoutes(fastifyInstance?)
Register request inspection routes (headers, ip, user-agent).
async registerResponseInspectionRoutes(fastifyInstance?)
Register response inspection routes (cache, etag, response-headers).
async registerResponseFormatRoutes(fastifyInstance?)
Register response format routes (json, xml, html, etc.).
async registerRedirectRoutes(fastifyInstance?)
Register redirect routes (absolute, relative, redirect-to).
async registerCookieRoutes(fastifyInstance?)
Register cookie routes (get, set, delete).
async registerAnythingRoutes(fastifyInstance?)
Register "anything" catch-all routes.
async registerAuthRoutes(fastifyInstance?)
Register authentication routes (basic, bearer, digest, hidden-basic).
async registerImageRoutes(fastifyInstance?)
Register image routes (jpeg, png, svg, webp) with content negotiation support.
Taps (Response Injection)
Access the TapManager via mockHttp.taps to inject custom responses.
taps.inject(response, matcher?)
Injects a custom response for requests matching the criteria.
Parameters:
response(InjectionResponse | InjectionResponseFunction):- Static Response (InjectionResponse):
response: string | object | Buffer - The response bodystatusCode?: number - HTTP status code (default: 200)headers?: object - Response headers
- Function Response (InjectionResponseFunction):
- A function that receives the Fastify request object and returns an InjectionResponse
(request: FastifyRequest) => InjectionResponse- Allows dynamic response generation based on request properties (url, method, headers, etc.)
- Static Response (InjectionResponse):
matcher?(InjectionMatcher) - Optional matching criteria:url?: string - URL path (supports wildcards with*)method?: string - HTTP method (GET, POST, etc.)hostname?: string - Hostname to matchheaders?: object - Headers that must be present
Returns: InjectionTap - A tap object with a unique id that can be used to remove the injection
taps.removeInjection(tapOrId)
Removes an injection.
Parameters:
tapOrId: InjectionTap | string - The tap object or tap ID to remove
Returns: boolean - true if removed, false if not found
taps.injections
A getter that returns a Map of all active injection taps.
Returns: Map<string, InjectionTap> - Map of all active injections with tap IDs as keys
taps.clear()
Removes all injections.
taps.hasInjections
A getter that returns whether there are any active injections.
Returns: boolean - true if there are active injections, false otherwise
About mockhttp.org
mockhttp.org is a free service that runs this codebase and allows you to use it for testing purposes. It is a simple way to mock HTTP responses for testing purposes. It is globally available has some limitations on it to prevent abuse such as requests per second. It is ran via Cloudflare and Google Cloud Run across 7 regions globally and can do millions of requests per second.
Contributing
Please read our CODE OF CONDUCT and CONTRIBUTING for details on our code of conduct, and the process for submitting pull requests to us.
