List for cgit developers and users
 help / color / mirror / Atom feed
From: John Keeping <>
To: "Valdis Vītoliņš" <>
Subject: Re: Downloading objects hangs up around 65kB
Date: Sat, 17 Sep 2022 17:07:59 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Sep 16, 2022 at 10:55:39PM +0300, Valdis Vītoliņš wrote:
> Probably it is issue on 64-bit ARM architecture, because I tested that it
> works on x86_64 virtual machine.
> Some time ago (because I haven't used HTTPS protocol for repositories
> recently) downloading plain objects/blobs hangs up around 65kB of data.
> You can test it with:
> wget -O "01_About.odp" -d
> ""
> It shows:
> ...
> Saving to: ‘01_About.odp’
> 01_About.odp                        8%[====>                           ]
> 63,64K  13,0KB/s    in 4,9s
> 2022-09-16 22:32:33 (13,0 KB/s) - Connection closed at byte 65169. Retrying.
> ...
> etc.

This seems very strange (it also happens with the .../tree/... pages
showing the hexdump file content).

My guess is that this is caused by the Apache configuration rather than
anything CGit is doing itself.

Have you tested running cgit outside Apache using something like:

	CGIT_CONFIG=/path/to/cgitrc \
	QUERY_STRING=url=JTM/plain/doc/presentations/01_About.odb \

That should give some idea whether CGit itself is returning short data
or if the response is being truncated downstream.


  reply	other threads:[~2022-09-17 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 19:55 Valdis Vītoliņš
2022-09-17 16:07 ` John Keeping [this message]
2022-09-17 20:04   ` Valdis Vītoliņš

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).