You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,8 +41,10 @@ Reqable uses the classic MITM proxy method for debugging and supports such as re
41
41
-[x] Mirroring: Configure mirror mapping for the specified domain name and port.
42
42
-[x] API testing: Compose APIs from the recording list.
43
43
-[x] History: Automatically save the recording list for easy retrospective viewing.
44
+
-[x] Diff tool: Compare request and response messages, quickly locate data deviations.
44
45
-[x] Replay: Support single or multiple requests for playback testing.
45
-
-[x] Auto-Highlighting: Support preset rules to highlight requests.
46
+
-[x] Reverse proxy: Use local reverse proxy server to debug HTTPS traffics without trusting CA certificate.
47
+
-[x] Traffic source: Detect which application the traffic is coming from.
46
48
-[x] HAR: Automatically associate HAR files, and support HAR export and open.
47
49
48
50
Real machine screenshot:
@@ -54,6 +56,7 @@ Real machine screenshot:
54
56
Reqable can compose API for testing and also supports features such as API collection and history.
55
57
56
58
-[x] Supports HTTP/1.1, HTTP2 and HTTP3 (QUIC) protocols.
59
+
-[x] API collection: Save API to collections, or import collections from Postman and Hoppscotch.
57
60
-[x] Multiple sessions: Support creating multiple Tabs for API testing.
58
61
-[x] Batch editing: Support batch editing of query parameters, request headers, forms, etc.
59
62
-[x] Authorization settings: Support authorization methods such as API KEY, Basic Auth, and Bearer Token.
@@ -69,7 +72,22 @@ Real machine screenshot:
69
72
70
73
## Mobile App
71
74
72
-
Reqable plans to launch a standalone mobile app. But I am currently still focusing on the desktop, the development of the mobile app will start as early as September, it depends on the progress of the desktop. Reqable is developed using Flutter and C++ and needs to be adapted to some specific platforms and interactive methods. I believe that the first version of the mobile app will be released soon.
75
+
The Reqable mobile app can be used standalone or work with the desktop app. Standalone means that traffic recording and API testing can be performed independently without relying on the desktop. While in collaborative mode, the mobile app could automatically forward traffic to the desktop by scanning the desktop QR code without manually configuring the Wifi proxy.
76
+
77
+
#### Android
78
+
79
+
The Android version has been basically completed and is currently open for beta-testing, see [Github Release v2.0.0](https://github.com/reqable/reqable-app/releases). In order to limit the number of testers, it is only open to accounts with the annual license. Android implements most of the features on the desktop, except for some with legal risks, such as rewriting.
80
+
81
+
- On devices not lower than Android Q (API 29), Reqable Magic Service is an optional. Reqable will try to use the system api, but will not be able to detect the source app of the traffic belongs, and it may not be able to capture all the traffic.
82
+
- On devices lower than Android Q, the Reqable Magic Service is required, and recording cannot be enabled without installed.
83
+
84
+
Real machine screenshot:
85
+
86
+

87
+
88
+
#### iOS
89
+
90
+
The iOS version is still under preparation and will be open for beta-testing soon.
0 commit comments