Zaki/Password-Manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(android): a missing reply is not "HTTP 0"

Browse Source 
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>
This commit is contained in:
r-zakarya
2026-08-17 13:40:53 +01:00
parent c215a5755d
commit 74b20266b3
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mainApk.pas
+8 -2
View File
@@ -785,8 +785,14 @@ begin
LSw := TStopwatch.StartNew; LSw := TStopwatch.StartNew;
LRes := LClient.Fetch(FETag); LRes := LClient.Fetch(FETag);
LSw.Stop; LSw.Stop;
Log(' HTTP ' + LRes.HttpCode.ToString + ' in ' + // Un code a zero n'est pas un statut : c'est qu'aucune reponse HTTP
LSw.ElapsedMilliseconds.ToString + ' ms'); // 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 case LRes.Status of
ssNotModified: ssNotModified: