Skip to content

Releases: eolinker/apinto

v0.12.6

03 Apr 03:26
Compare
Choose a tag to compare

Changelog

  • 81f2e4d 修复kafka空指针的问题

v0.12.5

31 Mar 07:07
Compare
Choose a tag to compare

1、上游服务新增会话保持选项,带有同一个session的用户,会转发到同一个上游地址
2、修复静态服务发现健康检查无效的问题
3、修复ip-hash算法不生效的问题
4、修复灰度策略会话保持不生效的问题

Changelog

v0.12.4

17 Mar 12:11
Compare
Choose a tag to compare
  1. 修复应用多驱动时,鉴权失效的问题
  2. 部分非error打印改成debug
  3. 修复策略check时,path匹配和方法匹配失效bug
  4. 修复上游服务超市时间在gRPC、Dubbo2协议透传不生效的问题
  5. 修复策略模块筛选范围ip、上游不生效的问题

Changelog

  • a2468c9 Merge remote-tracking branch 'gitlab/hotfix/label'

v0.12.3

12 Mar 14:26
Compare
Choose a tag to compare

Changelog

  • 6db3ae7 Merge remote-tracking branch 'gitlab/main'

该问题仅当v0.12.2版本存在

v0.12.2

09 Mar 08:45
Compare
Choose a tag to compare

Changelog

v0.12.1

03 Mar 13:26
68da18d
Compare
Choose a tag to compare

New features

  1. 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.

  1. 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.

  1. 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.

Changelog

  • 68da18d Merge pull request #94 from eolinker/release/v0.12.0

v0.11.1

24 Feb 12:12
cf7da53
Compare
Choose a tag to compare
  1. The protocol conversion function is online and supports the protocol conversion between HTTP and gRPC, HTTP and Dubbo2.

  2. New transcode module.

  3. Connect to Prometheus.

Changelog

  • cf7da53 Merge pull request #91 from eolinker/release/v0.10.1

v0.10.1

23 Feb 03:55
6563753
Compare
Choose a tag to compare

Changelog

  • 6563753 Merge pull request #88 from eolinker/release/v0.10.1

v0.10.0

17 Feb 11:04
d449414
Compare
Choose a tag to compare

New features

  1. Support multi-protocol forwarding, including Dubbo2 and gRPC protocols.

GRPC route:

Dubbo2 route:

  1. New plug-ins: Dubbo2 request rewriting, gRPC request rewriting.

GRPC rewrite plug-in:

Dubbo2 rewrite plug-in:

  1. Fix the problem that the package of amd64 architecture cannot be deployed and installed on the Linux system during packaging.

Version Preview

  1. Access to Prometheus monitoring

  2. Add protocol conversion plug-in

  • Http to gRPC

  • Http to Dubbo2

......

Changelog

  • d449414 Merge pull request #87 from eolinker/release/v0.10.0

v0.9.1

07 Feb 09:26
Compare
Choose a tag to compare
  1. Fix the inconsistency between the monitoring request and proxy time

  2. Fix the problem of invalid anonymous application

  3. Fix the problem that the certificate configuration does not take effect due to timing problems

  4. Repair request failed with status code 200

Changelog