Description of problem: Currently the webserver for bugzilla sends a Connection: close header in each response and closes the connection. Therefore a webbrowser has to open a new connection for each requests. These requests are ssl encrypted and there it takes quite long to open a new connection. If keep-alive was enabled, the browser can reuse an establised connection and therefore it will take less time to request a complete bugzilla page.
Matt, is this something that we can now address with GIT to see if they we can enable this on our webapps?
This is something that we scrapped due to issues IT has seen with their other apps in the DC. If we were using some dedicated static content servers it would be useful, but for dynamic it's not so much.
(In reply to comment #2) > This is something that we scrapped due to issues IT has seen with their other > apps in the DC. If we were using some dedicated static content servers it > would be useful, but for dynamic it's not so much. There are a log of probably static CSS and Javascript files that get loaded for every request, there seem to be around 19 requests for such extra files for one bug report. Now each of these requests take at least the time for one SSL-Handshake, even if they return a 404.
As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
As noted previously, the Bugzilla Team is cleaning up a large number of outstanding issues that have bit rotted. This bug is being closed as there has been no response to that notification. If you believe this bug is still important please reopen this bug in the NEW status and PM will consider it.