HTTP Response Analyzer

Input Encoded Response

POST /api/user/register h2
Host: www.holwin123.icu
content-length: 187
sec-ch-ua-platform: "Android"
di: 663159c38121b7684aa80bb134ae7617
accept-language: en
sec-ch-ua: "Not;A=Brand";v="99", "Android WebView";v="139", "Chromium";v="139"
sec-ch-ua-mobile: ?1
vtoken: bad65090104ea5b35663d412f4d04fad
user-agent: Mozilla/5.0 (Linux; Android 12; V2205 Build/SP1A.210812.003_IN) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.7258.160 Mobile Safari/537.36
accept: application/json, text/plain, */*
content-type: application/json
origin: https://www.holwin123.icu
x-requested-with: mark.via.gp
sec-fetch-site: same-origin
sec-fetch-mode: cors
sec-fetch-dest: empty
referer: https://www.holwin123.icu/userRegister
accept-encoding: gzip, deflate, br, zstd
priority: u=1, i

{"mobile":"7862078779","authCode":"779584","password":"mrsahil123","inviteCode":"Y6VY6B","sourceAppType":"lobby","registerHost":"www.holwin123.icu","sourceUrl":"https://www.hlowin.link/"}

http response do (�/�X�# 0�<@mc�͒�?3����x��pʹ��c
aJ��j��n�c���Ԇ��CSx��6��mCŢ�/�<��"U��!܄�,E0��@�<�7��\z��m��1�H��/��tѭ�X����uP:ݴfZ�c/#*����U�R��3H
�BǯR

Analysis Results

Results will appear here after analysis...

Possible Decoded Response

Decoded content will appear here...

Common Issues

Compression - Responses may be gzip or deflate compressed
Encoding - Character encoding mismatches can cause garbled text
Binary Data - Responses may contain binary data that's not text
Chunked Encoding - Transfer-encoding can affect response parsing

How to Fix

Check the Content-Encoding header for compression type
Use appropriate decompression algorithms (gzip, deflate, br)
Verify the Content-Type header for correct encoding
Ensure your HTTP client properly handles compressed responses

Response Headers to Check

Content-Encoding - gzip, deflate, br
Content-Type - text/html, application/json, etc.
Transfer-Encoding - chunked
Content-Length - size of response body