Releases: eolinker/apinto
v0.12.9
v0.12.8
v0.12.7
v0.12.6
v0.12.5
v0.12.4
v0.12.3
v0.12.2
v0.12.1
New features
- New traffic image (eolinker. com: apinto: proxy_mirror) plug-in
The traffic mirroring (eolinker. com: apinto: proxy_mirror) plug-in provides the ability to mirror client requests. Traffic mirroring is to copy the real online traffic to the mirroring service, so that the online traffic or request content can be specifically analyzed without affecting the online service.
- Add the http mocking (eolinker. com: apinto: http_marking) plug-in
API Mock is a technology that allows programmers to simulate the response of web server-side APIs without relying on back-end data. API Mock is usually used to test front-end applications without waiting for back-end programmers to build them. API Mock can simulate any HTTP request method and perform response tests.
Apintoprovides HTTP Mocking plug-in to simulate Api Mock request response data. It is not necessary to wait for the back-end interface to go online, and debug the front-end application through the simulation data.
- Rich http routing features and support static resource routing
Before ApINTO v0.12, if the client wants to obtain static resources, it still uses the proxy to forward to the upstream service to obtain resources, which is time-consuming and laborious, and increases the pressure on the upstream service. It is not advisable. In order tosolve this problem, ApINTO v0.12 added static resource routing, which can set the default return of the interface to meet the client requirements, including static HTML pages, static interface data (Json, XML and other format data), page redirection, and so on.