https://github.com/thewraven/cache
A boring, dead simple http proxy.
https://github.com/thewraven/cache
go http http-mocking http-proxy
Last synced: 3 months ago
JSON representation
A boring, dead simple http proxy.
- Host: GitHub
- URL: https://github.com/thewraven/cache
- Owner: thewraven
- Created: 2018-01-30T04:40:39.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2020-05-19T21:36:01.000Z (almost 6 years ago)
- Last Synced: 2024-06-20T15:45:10.740Z (almost 2 years ago)
- Topics: go, http, http-mocking, http-proxy
- Language: Go
- Size: 7.81 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Cache
## What exactly `cache` does?
The purpose of `cache` is to create N HTTP server proxies that intercept requests, make the request to the actual server and persists both request and response info (body + headers). Then the client receives the response transparently. If somebody requests the same resource again, it will get
the `cached` response.
## Why?
With `cache`, you can make quick n' dirty integration tests. Sometimes you don't have the time to mock all your services, or you have to replicate an special scenario or play around with the header responses. `Cache` helps you to inspect your requests and responses.
## Installation
If you have a `Go` installation you can get the development version:
> go get -u github.com/thewraven/cache
the fresh binary is in your `$GOPATH/bin` folder.
If you want a ready-to-use binary, you can grab'em [here](https://github.com/thewraven/cache/releases).
## Usage
> cache -config yourservers.json
`yourservers.json` defines the proxies that will be run.
This is an example of a simple server configuration.
* Remote: the `ip:port` of the real server.
* Local: the `ip:port` of the proxy.
* Cache: if it is set to `true`, it'll reuse the latest response of the real server.
* Timeout (minutes): After `x` minutes, the latest server response will be invalidated.
* Cache_path: Folder when the requests and responses will be persisted.
You can define an array of configurations, `cache` will spawn as many servers as required.
```json
[
{
"remote": "yourrealserver.com:8888",
"local": ":9999",
"cache": true,
"timeout_minutes": 10,
"cache_path": "your_cache_folder"
}
]
```