#11 Ziproxy don\\\\\\\'t compress bugzilla bugs\\\\\\\' lists

[Anonymous]

Consider these examples:

http://bugs.winehq.org/buglist.cgi?email1=t.artem%40mailcity.com&emailtype1=exact&emailreporter1=1

or this one:

http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.1&target_milestone=4.0.4&target_milestone=4.1.2&target_milestone=4.2.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

// Artem S. Tashkinov

[Daniel Mealha Cabrita]

Logged In: YES
user_id=1295112
Originator: NO

Actually this issue is more like a limitation of Ziproxy than a bug itself.

The problem with both pages is this:
Content-Type: multipart/x-mixed-replace

Ziproxy's internal structure is not meant for individual chunk processing, it only sees the data as big file (not a series of text/html etc).

There are two possible approches:

1. - To force User-Agent: into something different than Mozilla/Firefox, like Konqueror.
This way, we'll force the httpd to send the data in the conventional way (broken in several files) since Apache thinks Konqueror (or another browser) does not support multipart/x-mixed-replace.
Unfortunately Apache ignores Accept: claiming multipart/x-mixed-replace as non-supported (it should not, but what can we do).
Apache uses User-Agent: in order to determine such capability, so we would need to change that.
The problem by doing this: there will be compatibility problems, or worse, some sites will simply refuse to work with a different user-agent.

2. - To simply allow gzipping of multipart/x-mixed-replace.
I'm not sure it's going to work properly.
Also, that would be only effective for text/* data though, and htmlopt and preemptdns won't work with such data still.

3. - To rewrite Ziproxy changing its structure into something more scalable, so we could treat such data properly.
Technically the best option, unfortunately I've got no time for such work.

Anyways, I'm open to ideas.