incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver-Rainer Wittmann <orwittm...@googlemail.com>
Subject Re: update service - proposal for temporary solution until AOO 3.4 is released.
Date Wed, 21 Mar 2012 09:24:00 GMT
Hi,

On 21.03.2012 09:48, Oliver-Rainer Wittmann wrote:
> [snip...]
>>
>> a final note on this...if I directly put
>>
>> UpdateURL=http://www.openoffice.org/ProductUpdateService/check.Update<http://people.apache.org/%7Earielch/ProductUpdateService/check.Update?pkgfmt=rpm>
>>
>>
>> in my versionrc file, it works per Ariel's comments -- 'No Update
>> Available".
>>
>> However, my redirect via /etc/hosts causes the weird result. So maybe
>> something is not quite right with this (???)
>>
>>
>
> It looks like your local 'redirection' does not work.
>
> You can check your 'redirection' in your browser.
>
> On my system (Windows 7) I observe the following:
> - browsing to www.openoffice.org/ProductUpdateService/check.Update using FireFox
> shows me the XML snippet.
> - a ping to www.openoffice.org reveals IP address 140.211.11.131.
> - browsing to 140.211.11.131/ProductUpdateService/check.Update using FireFox
> return "404 Not Found".
> - browsing to 140.211.11.311 using FireFox shows ASF main page.
> - adapting my ...\etc\hosts file as you have done and browsing to
> update36.services.openoffice.org/ProductUpdateService/check.Update using FireFox
> results in a connection time stating the standard message which is headed by
> "The connection was reset" - the same you got when you browse to a non-existing
> server
> - reverting the change to my ...\etc\hosts and performing a ping to
> update36.services.openoffice.org outputs the following:
> <output>
> $ ping update36.services.openoffice.org
>
> Pinging sd-web2.staroffice.de [192.18.197.109] with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.18.197.109:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> </output>
>
>

BTW, the used HTTP/WebDAV client library and its integration into our UCB is 
able to handle HTTP redirects which are typically triggered by return HTTP 
status code 301 - HTTP status codes 302, 303 and 307 are also handled.

Best regards, Oliver.

Mime
View raw message