Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Critical: Satellite 6.16.0 release), and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:8906

OK, following the reproducer (go to login page, open dev console Network tab and press Ctrl+Shift+R), we are on 24 MB which is 20% improvement. IMO that is good enough for now.

Tested on 6.16.0 (satellite-6.16.0-0.5.stream.el8sat.noarch & foreman-3.12.0-0.1.develop.20240724143215git175b5f2.el8sat.noarch & katello-4.13.0-0.1.master.el8sat.noarch).

This https://brr.fyi/posts/engineering-for-slow-internet could be a nice read for anybody working on any web app (it is from a guy doing IT things on some Antarctica US base):

> If you’re an app developer reading this, can you tell me, off the top of your head, how your app behaves on a link with 40 kbps available bandwidth, 1,000 ms latency, occasional jitter of up to 2,000 ms, packet loss of 10%, and a complete 15-second connectivity dropout every few minutes?

As part of https://projects.theforeman.org/issues/37252 we reduced the duplication greatly so I'm moving this to In Review.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.