From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arunisaac@systemreboot.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=systemreboot.net;
	s=default; t=1784591746;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=whN3mj/dttGKHVmFLDvWdELFd7NSl+HYAFc2Ou9Pvr8=;
	b=KwwHl7KyXExS3VLXMBKPicjEl+Jf8vYuC3/CoZJldD+cdVTBpZQlyFvt07LXva7ygxqRFR
	BpjpQuh5H0xtcAcxuKYmQMZDOPmEYZYBSyTr9KBt6POpW5seszoOcfDuuZVRQJtuEWGaP1
	oSg+iZIuRMU/TIeWjReIJSSLkGiLd9gatbilBwFMx8KNYUvlvxO9yQOlxKhyycl7GgV3L5
	2D6sxwuT39jaeqTiHZRPS7EireuCJl9NphltDx6Sy6Yh5xR9Sgq4KT28yHH5/XK5WdjNrh
	FZU00ZrysotjkWbOcPLoW5XHcDSyK59jqo22ZAtpzwG8VyyaTTABr48+8wUKdg==
Received: from localhost (<unknown> [192.168.2.1])
	by mugam.systemreboot.net (OpenSMTPD) with ESMTPSA id e14c339c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO);
	Mon, 20 Jul 2026 23:55:46 +0000 (UTC)
From: Arun Isaac <arunisaac@systemreboot.net>
To: jgart <jgart@dismail.de>, kaagum@systemreboot.net
Subject: Re: [PATCH] Remove #:streaming? #t from HTTP requests to fix JSON
 parsing
In-Reply-To: <20260720142610.1193079-1-jgart@dismail.de>
References: <20260720142610.1193079-1-jgart@dismail.de>
Date: Tue, 21 Jul 2026 00:55:44 +0100
Message-ID: <87zezlgqrj.fsf@systemreboot.net>
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <kaagum.systemreboot.net>


Hi jgart,

I don't think guile does automatic gzip decompression regardless of
#:streaming?. Here's a snippet below that tests guile's http-get against
the /gzip endpoint of the https://httpbin.org/ service. In both cases, I
get a bytevector. That means, there is no gzip decompression either way.

(use-modules (web client)
             (srfi srfi-71)
             (rnrs io ports))

(let ((response body (http-get "https://httpbin.org/gzip")))
  (pk body))

(let ((response body (http-get "https://httpbin.org/gzip"
                               #:streaming? #t)))
  (pk (get-bytevector-all body)))

Could you provide more details about which LLM provider you were using
and how you ran into the bug with the invalid JSON error?

> I also noticed that openai-models was working around this with an
> accept-encoding: identity header.

I'm not sure what workaround you are referring to.

Thanks,
Arun