Cold load of consumption page shows "stream timeout"

Deebster

When loading the consumption page, if you have been on it recently it is immediate, but with enough time the page will just show the error message "stream timeout". You can always refresh after a stream timeout message and see the page immediately.

FWIW, I'd rather have a longer wait than have the page XHR in the results.

(This isn't specifically search related, but there isn't a general Kagi.com category).

RoxyRoxyRoxy

Hey, I can't replicate this (though the first load was a bit slow). Do you still see this occurring?

Deebster

Yes, this is an old issue and I've seen it across browsers and devices. I just triggered it again, but failed to get the headers. I'll try figure out how cold it needs to be to work (my last visit was six days ago, but I think the threshold is something more like 10 hours).

I should have mentioned that I am connecting to ASIA-SOUTHEAST.

Deebster

I've trigger it after a gap of ~6h.

Response:

stream timeout

Response headers:

HTTP/3 504 
content-length: 14
content-type: text/plain
via: 1.1 google
date: Sat, 11 Oct 2025 09:03:03 GMT
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000; includeSubDomains; preload
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

Timings:

Hitting refresh loads the page straight away (87ms).

Deebster

Another try at date: Sun, 12 Oct 2025 04:19:23 GMT

I'll keep gathering data to see if it's always 10s.

Deebster

date: Sun, 12 Oct 2025 14:02:33 GMT

Seems like it.

Deebster

date: Mon, 13 Oct 2025 02:39:34 GMT
Waiting: 10.81s

Seems pretty consistent, so now I only don't know the required cold interval.

Deebster

The threshold before it starts failing seems to be about 4 hours.

I'm calling it without going through the settings, just reloading the old page in the browser or calling via curl:

$ wget -O /dev/null --tries=1 --server-response --header $cookie https://kagi.com/settings/consumption
--2025-10-24 08:04:42--  https://kagi.com/settings/consumption
Resolving kagi.com... 2600:1901:0:daa1::, 34.111.242.115
Connecting to kagi.com|2600:1901:0:daa1::|:443... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 504 Gateway Timeout
  Content-Length: 14
  content-type: text/plain
  via: 1.1 google
  date: Fri, 24 Oct 2025 01:04:51 GMT
  X-Frame-Options: SAMEORIGIN
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
  Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Giving up.