public inbox for kaagum@systemreboot.net
 help / color / mirror / Atom feed
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
Date: Tue, 21 Jul 2026 00:55:44 +0100	[thread overview]
Message-ID: <87zezlgqrj.fsf@systemreboot.net> (raw)
In-Reply-To: <20260720142610.1193079-1-jgart@dismail.de>


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

  parent reply	other threads:[~2026-07-20 23:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 14:21 jgart
2026-07-20 14:21 ` [PATCH] Remove #:streaming? #t from HTTP requests jgart
2026-07-20 23:55 ` Arun Isaac [this message]
2026-07-21  8:51   ` [PATCH] Remove #:streaming? #t from HTTP requests to fix JSON parsing jgart
2026-07-21 23:43     ` Arun Isaac
2026-07-22  3:31       ` jgart
2026-07-22 11:03         ` Arun Isaac
2026-08-14 11:52           ` jgart
2026-08-14 13:01             ` Arun Isaac

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zezlgqrj.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=jgart@dismail.de \
    --cc=kaagum@systemreboot.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox