yuanbiao/emqx
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0bb4308a48
emqx/apps/emqx_bridge_http
History
Kjell Winblad 15594b4db6 fix(HTTP connector): retry on 503 Service Unavailable response 
Previously, if an HTTP request received a 503 (Service Unavailable)
status, it was marked as a failure without retrying. This has now been
fixed so that the request is retried a configurable number of times.

Fixes:
https://emqx.atlassian.net/browse/EMQX-12217
https://github.com/emqx/emqx/issues/12869 (partly)
2024-04-25 17:05:18 +02:00
..
src fix(HTTP connector): retry on 503 Service Unavailable response 2024-04-25 17:05:18 +02:00
test fix(HTTP connector): retry on 503 Service Unavailable response 2024-04-25 17:05:18 +02:00
README.md refactor: HTTP connector into emqx_bridge_http app 2023-07-12 14:46:43 +02:00
rebar.config style: erlfmt all rebar.config files and bin/nodetool 2023-12-29 09:08:03 +08:00

README.md

EMQX HTTP Broker Bridge

This application enables EMQX to connect to any HTTP API, conforming to the HTTP standard. The connection is established via the HTTP bridge abstraction, which facilitates the unidirectional flow of data from EMQX to the HTTP API (egress).

Users can define a rule and efficiently transfer data to a remote HTTP API utilizing EMQX Rules.

Documentation

  • For instructions on how to use the EMQX dashboard to set up an egress bridge, refer to Bridge Data into HTTP API.

  • To understand the EMQX rules engine, please refer to EMQX Rules.

HTTP APIs

We provide a range of APIs for bridge management. For more detailed information, refer to API Docs -Bridges.

Contributing

For those interested in contributing, please consult our contributing guide.

License

This software is under the Apache License 2.0. For more details, see LICENSE.