Question 1

How do I simulate dynamic API responses with DeepfakeHTTP?

Accepted Answer

Use JavaScript handlers via the X-Handler-JS header in dump files, which allow you to write functions that process requests and generate responses dynamically, as explained in the appendix with examples.

Question 2

DeepfakeHTTP vs json-server: which is better for local development?

Accepted Answer

DeepfakeHTTP offers more flexibility with HTTP dump matching and dynamic handlers, while json-server is simpler for RESTful CRUD operations. Choose DeepfakeHTTP if you need precise control over request-response pairs.

Question 3

Can DeepfakeHTTP handle authentication in mock APIs?

Accepted Answer

Yes, by including authentication headers in the dump file requests. Use wildcards or templates to match varying tokens, or script authentication logic in JavaScript handlers for dynamic validation.

Question 4

How to add delay to responses in DeepfakeHTTP?

Accepted Answer

Use the X-Delay header in the response part of the dump file, specifying milliseconds. For example, 'X-Delay: 2000' adds a two-second delay, as shown in the optional headers section.

Question 5

Does DeepfakeHTTP support GraphQL mocking?

Accepted Answer

Yes, it can mock GraphQL APIs by recording HTTP exchanges in dump files, since GraphQL typically uses HTTP POST. You can also use JavaScript handlers to parse and respond to GraphQL queries dynamically.

Question 6

How to set up HTTPS with DeepfakeHTTP?

Accepted Answer

Use the --port-ssl option to enable HTTPS on a specified port with a built-in self-signed certificate. Combine with --redirect to automatically redirect HTTP to HTTPS for secure connections.

DeepfakeHTTP

What is DeepfakeHTTP?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions