Skip to content

Update README to include link to SWHttpTrafficRecorder. #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JinlianWang wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README to include link to SWHttpTrafficRecorder. #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,10 @@ So we made one up. It's newline-delimited.
Everything after the response headers section (i.e. the blank line after line 4) is sent back as the response body, either verbatim or Base64-decoded, depending on what content type you put in the response headers. Unless you use the placeholder support, but more on that later.
It doesn't even matter what the filename is as long as it ends in `.tail`. You just use one of these files per mock response "endpoint" and Mocktail loads them all in when you start it.

##### Notes

There are tools that can record all the HTTP(s) traffic in the background while the app is running in the exact file format described here, like [SWHttpTrafficRecorder](https://github.com/capitalone/SWHttpTrafficRecorder). After recording, the files can be used by Mocktail to stub out HTTP servers.

## Placeholder support

Oh, so you wanted your mock responses to be smarter? That's not very slacker-like.
Expand Down