https://ilham.dev/tags/debugging/Recent content in Debugging on ilham.devHugo -- gohugo.ioenSun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-break-a-url-into-parts/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-break-a-url-into-parts/A URL contains several parts: scheme, host, path, query string, and sometimes a fragment. Debugging is easier when those parts are separated. The URL Parser tool helps me inspect the input and output without writing a one-off script first.https://ilham.dev/posts/how-to-check-browser-network-information/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-check-browser-network-information/Browser network APIs may expose hints about connection type or device context, but availability varies by browser and privacy settings. The Network Info tool helps with the mechanical part, but I still check the result before using it somewhere real.https://ilham.dev/posts/how-to-check-browser-device-information/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-check-browser-device-information/A browser can reveal useful debugging context such as screen size, user agent hints, language, and platform, but not a complete identity. The Device Information tool helps with the mechanical part, but I still check the result before using it somewhere real.https://ilham.dev/posts/how-to-build-dns-and-network-notes-from-small-tools/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-build-dns-and-network-notes-from-small-tools/Network debugging usually needs more than one clue. DNS, IPs, ports, URLs, and headers each answer a different question. I use Network tools for the quick version of this task, then I review the output before relying on it.https://ilham.dev/posts/how-to-compare-two-text-blocks-line-by-line/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-compare-two-text-blocks-line-by-line/A text diff shows what changed between two blocks of text. It is useful for configs, logs, snippets, and documentation. The Text Diff tool helps me inspect the input and output without writing a one-off script first.https://ilham.dev/posts/how-to-parse-a-websocket-frame/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-parse-a-websocket-frame/Most WebSocket debugging happens at the message level, but sometimes a raw frame needs to be decoded. I use WebSocket Frame Parser for the quick version of this task, then I review the output before relying on it.https://ilham.dev/posts/how-to-parse-logs-before-searching-randomly/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-parse-logs-before-searching-randomly/Logs become easier to investigate when they are split into fields instead of treated as one giant wall of text. The Log Parser tool gives me a safe place to test the idea before I put it into a script, server, or production workflow.https://ilham.dev/posts/how-to-read-a-user-agent-string/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-read-a-user-agent-string/A user-agent string can hint at browser, engine, operating system, and device, but it is messy and sometimes intentionally misleading. The User Agent Parser tool helps me inspect the input and output without writing a one-off script first.https://ilham.dev/posts/how-to-test-websockets-from-the-browser/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-test-websockets-from-the-browser/WebSockets keep a connection open so client and server can exchange messages in real time. The WebSocket Tester tool gives me a safe place to test the idea before I put it into a script, server, or production workflow.https://ilham.dev/posts/how-to-use-json-viewer-for-large-api-responses/Sun, 27 Sep 2026 00:00:00 +0700https://ilham.dev/posts/how-to-use-json-viewer-for-large-api-responses/A JSON viewer is for exploring structure. It helps me see objects, arrays, nested fields, and repeated records without reading one long block of text. The JSON Viewer tool is useful because it lets me check the result in a small, controlled place before I use it in a bigger workflow.