Don’t (server)push me

Bugzilla serves search results as multipart/x-mixed-replace, a mime-type which lets it send the “Please stand by…” page, have that displayed, and then replace it with the search results once the query completes. That’s probably fairly tolerable if you have a fast connection, a slow Bugzilla, and typically small queries. Me, I don’t.

I tend to do triage, when I do it, with broad “Find a Specific Bug” queries including closed bugs, to pull in all the synonyms that appear in duplicates, and sometimes (for narrow enough components, like Password Manager) with bookmarked searches for every open bug in a component, and I’m doing that over dialup. The “Please stand by…” splashscreen is tolerable enough, but then as my 200 results trickle in, and I scroll down them and find the bug I was after while the page is still loading, I start to get the second set of replaced content, so that my click on the link doesn’t actually load the bug I want, it just hurries along the re-loading of the same list that had already served its purpose. That’s particularly annoying when I click a bug link, switch to another tab (to do something like start the process of marking a duplicate) only to come back and find that the tab that should have my dupe target still has the results list that has my target in it. Somewhere.

Luckily, the other day I was reading buglist.cgi and discovered that I can quite often avoid the multipart/x-mixed-replace, because any URL that includes &serverpush=0 just gets served straight text/html. Fixing the search forms would require a bookmarklet, or more usefully a Greasemonkey script, to insert a <input type="hidden" name="serverpush" value="0"> in the form, but for my main bookmark and quicksearch use, just adding it to the URL makes using Bugzilla vastly more pleasant. Of course, I really ought to fix bug 298995 to get a user pref to turn it off completely, but now that my itch is scratched…

5 Comments

Comment by Jesse Ruderman #
2005-12-07 23:24:46

As far as I know, Bugzilla sends ”Please Stand By…” as one text/html part and sends the buglist as a second text/html part. It doesn’t send the buglist twice. Perhaps you’re hitting a browser bug that causes it to reload the page?

Comment by Phil Ringnalda #
2005-12-08 00:04:58

And of course, thanks to Heisenberg’s First Law Of Mentioning Bugs Or That Strange Noise Your Car Made Until You Got To The Mechanic’s, now I only managed to see it once in twenty attempts, but I think you’re probably right: I’d forgotten after seeing it so many times, but the ”Please Stand By…” does very briefly show up again, so it may well be something more like networking getting impatient and deciding to just start over. If I can get back to getting it consistently, I’ll run an HTTP log and see if it admits anything about what’s actually happening.

 
 
Comment by mcsmurf #
2005-12-08 06:38:07

Yeah this is very annoying even with broadband when you have a large buglist. You wait for it to load and suddenly *plop* it decides to reload that buglist fors
ome strange reason. Probably that’s a browser bug so?
let’s if see this works, i try to sign this message :)

 
Comment by tuukka #
2005-12-08 08:43:41

bug 61363 (bug 248610), perhaps.

 
Comment by Laurens Holst #
2005-12-08 14:56:55

I often load a bug, and when the bug including all the comments is loaded, it reloads the entire bug page again.

I don’t know whether this is the same thing, but it sure is annoying.

~Grauw

 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <del datetime="" cite=""> <dd> <dl> <dt> <em> <i> <ins datetime="" cite=""> <kbd> <li> <ol> <p> <pre> <q cite=""> <samp> <strong> <sub> <sup> <ul> in your comment.