Phone HTTP Test Client
Contains ads
Everyone
info
0+
Downloads
Everyone
Learn more
About this app
Phone HTTP Test Client sends HTTP or HTTPS requests from your smartphone and shows what the server answers. Check an MCU web server or a development API right away, without a laptop.
Main features
• GET, POST, PUT, PATCH and DELETE requests
• Enter the URL, headers and body (none, JSON or text)
• See the status code, headers, body, time, size and final URL
• View a body as JSON, text or HEX
• 400, 404 and 500 are shown as responses; connection failures by their cause
• Refused, DNS failure, connection timeout, response timeout and certificate errors told apart
• Timeout setting and request cancel
• History and resend (back into the form, so you can change it first)
• Check a self-signed development certificate by its SHA-256 fingerprint, trust it and manage the list
• GET /status and POST /sensor examples to start from
• A user guide with pictures, Korean and English
• No login: everything runs on your phone
Good for
• Checking the web server API of an MCU such as ESP32 in the field
• Sending POST and PUT requests that are awkward from a browser
• Checking responses and error handling of a development server
Please note
• POST, PUT, PATCH and DELETE can really change the other device. Send them only to servers you are allowed to use.
• HTTPS certificates are verified by default. There is no setting that accepts every certificate.
• Trust a self-signed certificate only when it matches the fingerprint from the server. A changed certificate is refused again.
• History stays on this device. Authorization, Cookie and API key values are not stored, but bodies can be.
• A response is read up to 8 MiB.
• Do not use it for safety-related control.
• The app shows ads. No interstitial appears while a request runs.
Main features
• GET, POST, PUT, PATCH and DELETE requests
• Enter the URL, headers and body (none, JSON or text)
• See the status code, headers, body, time, size and final URL
• View a body as JSON, text or HEX
• 400, 404 and 500 are shown as responses; connection failures by their cause
• Refused, DNS failure, connection timeout, response timeout and certificate errors told apart
• Timeout setting and request cancel
• History and resend (back into the form, so you can change it first)
• Check a self-signed development certificate by its SHA-256 fingerprint, trust it and manage the list
• GET /status and POST /sensor examples to start from
• A user guide with pictures, Korean and English
• No login: everything runs on your phone
Good for
• Checking the web server API of an MCU such as ESP32 in the field
• Sending POST and PUT requests that are awkward from a browser
• Checking responses and error handling of a development server
Please note
• POST, PUT, PATCH and DELETE can really change the other device. Send them only to servers you are allowed to use.
• HTTPS certificates are verified by default. There is no setting that accepts every certificate.
• Trust a self-signed certificate only when it matches the fingerprint from the server. A changed certificate is refused again.
• History stays on this device. Authorization, Cookie and API key values are not stored, but bodies can be.
• A response is read up to 8 MiB.
• Do not use it for safety-related control.
• The app shows ads. No interstitial appears while a request runs.
Send HTTP/HTTPS requests and check responses. Test APIs and MCU web servers.
Updated on
Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time.
