On Mon, 2021-08-16 at 13:55 -0300, Elias Pereira via samba wrote:> hi, > > I went to access the wiki and it is returning > the error ERR_HTTP2_PROTOCOL_ERROR. > > -- > Elias PereiraLouis emailed me about this, this morning. I told him what I am now telling you, it works for myself, perhaps it is something on the internet ?? Rowland
I believe not, Rowland. I asked several friends to try to access it, and they also informed me of the error. On Mon, Aug 16, 2021 at 2:13 PM Rowland Penny via samba < samba at lists.samba.org> wrote:> On Mon, 2021-08-16 at 13:55 -0300, Elias Pereira via samba wrote: > > hi, > > > > I went to access the wiki and it is returning > > the error ERR_HTTP2_PROTOCOL_ERROR. > > > > -- > > Elias Pereira > > Louis emailed me about this, this morning. I told him what I am now > telling you, it works for myself, perhaps it is something on the > internet ?? > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Elias Pereira
On Mon, Aug 16, 2021 at 1:13 PM Rowland Penny via samba <samba at lists.samba.org> wrote:> > On Mon, 2021-08-16 at 13:55 -0300, Elias Pereira via samba wrote: > > hi, > > > > I went to access the wiki and it is returning > > the error ERR_HTTP2_PROTOCOL_ERROR. > > > > -- > > Elias Pereira > > Louis emailed me about this, this morning. I told him what I am now > telling you, it works for myself,I'm also seeing errors using Chrome 92 and curl 7.64.0: $ curl https://wiki.samba.org/index.php/Main_Page curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) I am *not* seeing the issue with Firefox 78.13.0esr.> perhaps it is something on the internet ??I don't think so... this is likely an issue with the wiki.samba.org web server or proxy, and not some sort of global routing or DNS issue.
On 2021/08/16 10:13, Rowland Penny via samba wrote:> Louis emailed me about this, this morning. I told him what I am now > telling you, it works for myself, perhaps it is something on the > internet ?? >---- It's a similar example of the internet becoming unreadable for those who don't have the correct (or latest, or approved) "security" or "protocol" libraries installed on their system. I regularly see similar messages trying to download rpm files from/for my distro. I try to d/l a file w/o encryption using 'http', but if a mirror redirector directs me to an https-only, there was a while where I often got: 500 Can't connect to mirrors.edge.kernel.org:443 (SSL connect attempt failed with unknown error error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure) Took me a while, but I wasn't sure which SSL libs needed an upgrade. Finally, I either got the right libs, or the error went away. It was intermittent based on what mirror you got sent to. Some sites still allowed http, whereas others had a different version of SSL that worked with my machine's version. Somehow I found it ironic how downloading 'open source' files *required* encryption, ignoring the topic of needing "matching encryption". If someone with one of today's computers was to try using it in a decade, they might find they can't access much of the web -- a bit disturbing.