From 74b20266b3f51a2dacd4c535f11463aca62e061f Mon Sep 17 00:00:00 2001
From: r-zakarya <82443831+r-zakarya@users.noreply.github.com>
Date: Mon, 17 Aug 2026 13:40:53 +0100
Subject: [PATCH] fix(android): a missing reply is not "HTTP 0"

The log printed "HTTP 0 in 2013 ms" when no HTTP response arrived at all.
Zero is not a status code, and written that way it reads like one the server
returned - which sends you looking for the cause on the wrong side of the
connection. It now says "no HTTP reply after ... ms".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 mainApk.pas | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/mainApk.pas b/mainApk.pas
index b08ebc6..b31899c 100644
--- a/mainApk.pas
+++ b/mainApk.pas
@@ -785,8 +785,14 @@ begin
         LSw := TStopwatch.StartNew;
         LRes := LClient.Fetch(FETag);
         LSw.Stop;
-        Log('  HTTP ' + LRes.HttpCode.ToString + ' in ' +
-            LSw.ElapsedMilliseconds.ToString + ' ms');
+        // Un code a zero n'est pas un statut : c'est qu'aucune reponse HTTP
+        // n'est arrivee. Ecrit tel quel, il se lisait comme un vrai code rendu
+        // par le serveur, ce qui envoie chercher la cause du mauvais cote.
+        if LRes.HttpCode > 0 then
+          Log('  HTTP ' + LRes.HttpCode.ToString + ' in ' +
+              LSw.ElapsedMilliseconds.ToString + ' ms')
+        else
+          Log('  no HTTP reply after ' + LSw.ElapsedMilliseconds.ToString + ' ms');
 
         case LRes.Status of
           ssNotModified: