On 19 Aug, Dave Fisher wrote: > > >> On Aug 19, 2020, at 1:24 PM, Matthias Seidel <matthias.sei...@hamburg.de> >> wrote: >> >> Hi Dave, >> >> Am 19.08.20 um 22:11 schrieb Dave Fisher: >>> >>>> On Aug 19, 2020, at 12:12 PM, Matthias Seidel <matthias.sei...@hamburg.de> >>>> wrote: >>>> >>>> Am 19.08.20 um 20:50 schrieb Dave Fisher: >>>>>> On Aug 19, 2020, at 11:45 AM, Matthias Seidel >>>>>> <matthias.sei...@hamburg.de> wrote: >>>>>> >>>>>> Am 19.08.20 um 18:55 schrieb Dave Fisher: >>>>>>>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel >>>>>>>> <matthias.sei...@hamburg.de> wrote: >>>>>>>> >>>>>>>> Am 19.08.20 um 18:10 schrieb Dave Fisher: >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>>> On Aug 19, 2020, at 8:37 AM, Matthias Seidel >>>>>>>>>> <matthias.sei...@hamburg.de> wrote: >>>>>>>>>> >>>>>>>>>> Am 19.08.20 um 01:18 schrieb Dave Fisher: >>>>>>>>>>> Do those ancient versions of OpenOffice handle redirection? >>>>>>>>>> Redirection will be done on the (web) server side. >>>>>>>>> Then we can do redirection within the httpd.conf for OpenOffice.org. >>>>>>>>> >>>>>>>>> Infra holds that in puppet. I’ll look for it and link it. >>>>>>>>> >>>>>>>>>> Until then we need to preserve the existing pages where OOo expects >>>>>>>>>> them. >>>>>>>>> Let’s change that before migration. >>>>>>>> Where do you want to put these pages? >>>>>>> I would want to put them on ooo-updates if that would work. >>>>>> The update feed is broken for longer now... >>>>>> We still need to find a working solution. >>>>> Do we have a bug that describes how the update feed is broken? >>>> One bug? ;-) This has been discussed so often and for so long I don't >>>> even know where to start... >>>> >>>> https://bz.apache.org/ooo/show_bug.cgi?id=127789 >>>> >>>> Most of the comments are pure speculation but: >>>> >>>> https://bz.apache.org/ooo/show_bug.cgi?id=127789#c39 >>>> >>>> is interesting. Although Pedro is wrong about the regression in code it >>>> shows that the update feeds located on openoffice.org can be reached. >>>> This might be due to the old web server we are using. >>>> The update feeds hosted in Apache SVN are not working for most of our >>>> users. >>>> >>>> Andrea knows more about it but basically AOO (4.1.x) is not able to >>>> connect to the update feed via https due to outdated SSL components. >>>> (Changing the update URL to http works but is a dirty hack and has no >>>> effect on released versions) >>> I made some comments. Like Pedro I suspect a regression in the code. >> >> It stopped working about two years ago (for 4.x.x) >> And it is working for 4.2.x and trunk with the same update feeds. >> >> I am still not convinced... ;-) > > The other thought is the version of openssl and/or curl used and which > versions got which upgrades. > >> >>> >>> Do you know where the update code is? >> >> Sorry, maybe some developer knows? > > Need to look at the history of > > (1) openssl > (2) curl > (3) and the code that uses those.
The version of openssl used by 4.1.7 is seriously out of date and doesn't support recent versions of TLS. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
