Re: Blocker issue 127789: Server error when looking for updates

[Andrea Pescetti <pe...@apache.org>]

On 29/10/2018 Matthias Seidel wrote:
> Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
>> https://bz.apache.org/ooo/show_bug.cgi?id=127789 ...
>> As I wrote in the issue, this could be an issue just with the ASF
>> network configuration and it may not require a fix at all.
> 
> This is also my guess.

Just for the record, I cannot reproduce it now and I have to correct 
what I reported last month: while testing 4.1.6-RC1 I've found that I 
had a stale cached DNS entry that was generating incorrect requests.

In other words, I've never been able to reproduce the error on my system.

> All I can say is that my builds for Windows from trunk do not have this
> issue. Other users reported, that earlier versions of AOO get connection
> to the update server without error message.

This could be DNS but also some bundled library that adopts stricter 
protocol checks on HTTPS.

Due to increasing restrictions, I think the only proper way to test it 
would be to put a fake update feed online for the (imaginary) 4.1.6 -> 
4.1.7 update and see if the 4.1.6 builds report it correctly. It won't 
have any impact on real users, provided we remove the test feed before 
4.1.6 is officially released.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Blocker issue 127789: Server error when looking for updates

[Andrea Pescetti <pe...@apache.org>]

Matthias Seidel wrote:
> There is already an (empty) update feed for 4.1.6. AOO 4.1.6 should just
> report it is "up to date" (like 4.2.0 does).

Yes, but unless we can monitor it on the server side this is only 
partial information: I mean, if 4.1.6-RC1 was set, by some mistake, to 
use the same feed as 4.1.5 the feeds would be broken and we would not be 
able to notice it.

Limited to these days of 4.1.6-RC1 testing, the two solutions are:
- Temporary invent a 4.1.7 and update the 4.1.6 feeds accordingly, at 
least for testing (this is best, since it will remove all doubts).
- Monitor on the server logs that 4.1.6 is actually served the proper 
XML file.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Blocker issue 127789: Server error when looking for updates

[Matthias Seidel <ma...@hamburg.de>]

Am 09.11.18 um 01:07 schrieb Andrea Pescetti:
> On 29/10/2018 Matthias Seidel wrote:
>> Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127789 ...
>>> As I wrote in the issue, this could be an issue just with the ASF
>>> network configuration and it may not require a fix at all.
>>
>> This is also my guess.
>
> Just for the record, I cannot reproduce it now and I have to correct
> what I reported last month: while testing 4.1.6-RC1 I've found that I
> had a stale cached DNS entry that was generating incorrect requests.
>
> In other words, I've never been able to reproduce the error on my system.
>
>> All I can say is that my builds for Windows from trunk do not have this
>> issue. Other users reported, that earlier versions of AOO get connection
>> to the update server without error message.
>
> This could be DNS but also some bundled library that adopts stricter
> protocol checks on HTTPS.
>
> Due to increasing restrictions, I think the only proper way to test it
> would be to put a fake update feed online for the (imaginary) 4.1.6 ->
> 4.1.7 update and see if the 4.1.6 builds report it correctly. It won't
> have any impact on real users, provided we remove the test feed before
> 4.1.6 is officially released.

There is already an (empty) update feed for 4.1.6. AOO 4.1.6 should just
report it is "up to date" (like 4.2.0 does).

Regards,

   Matthias

>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>