Issue 107150 - OOo claims to understand compressed extension update feeds, but does not handle them correctly
Summary: OOo claims to understand compressed extension update feeds, but does not hand...
Status: CLOSED FIXED
Alias: None
Product: ucb
Classification: Code
Component: code (show other issues)
Version: DEV300m64
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: b.osi.ooo
QA Contact: issues@ucb
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-23 17:06 UTC by b.osi.ooo
Modified: 2010-02-09 15:45 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description b.osi.ooo 2009-11-23 17:06:08 UTC
Using a webserver, with enabled compression, to deliver the extension update
feed, results in an error message that indicates, that OO can not handle such
feedback. How to reproduce:
Configure OOo to use an compressed delivered feed:
in file: program/versionrc
ExtensionUpdateURL=http://extensions.services.openoffice.org/ProductUpdateService/check.Update
or, if that does not exists anymore, use internal one:
ExtensionUpdateURL=http://vm-tbo2/check.Update.txt

Then start OOo:
Tools->Extension Manager
press button Check for Updates
Check checkbox: Show all updates
-> An error occurred: Premature end of data in tag feed line 2
Line: 434 column: 0

The apache server (vm-tbo2) is configured to use mod_deflate for .txt files
if http://vm-tbo2/check.Update would be used, the same file is delivered
uncompressed, which will not result in an error message in OOo. (same for using
http://updateext.services.openoffice.org/ProductUpdateService/check.Update which
is the current default in OOo)

-> please make OOo able to handle compressed update feed streams, since it would
reduce the traffic for each request from 400kB to 30kB
Comment 1 matthias.huetsch 2009-11-24 12:17:11 UTC
adding myself to CC ...
Comment 2 joachim.lingner 2009-11-24 14:02:29 UTC
cc'ed kso
Comment 3 joachim.lingner 2009-11-25 08:26:52 UTC
.
Comment 4 kai.sommerfeld 2009-11-26 15:27:44 UTC
Confirming bug on OOo side. Server side is okay. Taking over.
Comment 5 kai.sommerfeld 2009-11-26 15:28:43 UTC
.
Comment 6 kai.sommerfeld 2009-11-27 12:55:07 UTC
Fixed.

tbo: Please note that due to this bug we cannot simply activate compressed
response for any update feed request. OOo 3.2 (and earlier? needs to be
checked!) will claim to support this feature but will fail, as we know. Thus,
server-side should check the user-agent request header (e.g. "StarOffice 9
(300m64(Build:9446)[CWS:kso42]; MacOSX; x86; BundledLanguages=en-US)") to
determine the version of the requesting OOo, before sending a compressed response.
Comment 7 stx123 2009-11-27 15:39:12 UTC
If we can't tweak the server to respond based on the user agent we will have to
introduce a different URL (ie. server).
Comment 8 b.osi.ooo 2009-12-01 14:23:47 UTC
reopen, since it is related to get this to work:
To make this work, we need to change the URL with this CWS;
The new URL will be:
http://updateexte.services.openoffice.org/ExtensionUpdateService/check.Update
in file versionrc for entry: ExtensionUpdateURL

(ST is working to get the url, which will currently just point to
http://extensions.services.openoffice.org/ExtensionUpdateService/check.Update)
Comment 9 kai.sommerfeld 2009-12-01 15:33:48 UTC
.
Comment 10 kai.sommerfeld 2009-12-01 15:54:06 UTC
New ExtensionUpdateURL now in scp2/source/ooo/common_brand.scp. => Fixed.
Comment 11 stx123 2009-12-01 18:02:14 UTC
I added the hostname updateexte.s.ooo which now points to the osuosl site (oooapps).
tbo, are you going to clarify the settings of the server with osuosl so that
this new vhost works?
Comment 12 b.osi.ooo 2009-12-07 14:16:30 UTC
premature check: since no build is available with the new url, i modified an old
build, which contains already the 'compressed' fix, with the new url and checked
on macosx: fine - gzip delivered from host, OOo understood the content. (master
build would fail with new url, which should be checked just for verifying this fix.)
(side note: for some reason i couldn't reproduce the old behaviour error on
linux with a masterbuild?)
Comment 13 kai.sommerfeld 2010-01-11 10:47:22 UTC
tbo: Please verify.
Comment 14 kai.sommerfeld 2010-01-11 10:48:23 UTC
Oop. Wrong owner. Changing to tbo.
Comment 15 b.osi.ooo 2010-01-11 13:34:32 UTC
verified on win32;
New URL is in OOo settings;
zipped stream works;
Comment 16 b.osi.ooo 2010-02-09 15:45:05 UTC
integrated into master dev300m71 - closing