Page 1 of 3

Wiki broken

Posted: Tue Dec 22, 2020 3:05 pm
by B.Y.O.B.
The wiki looks broken on my end, see attachment. Does this also happen for others, or is it a problem on my PC only?

Re: Wiki broken

Posted: Tue Dec 22, 2020 3:58 pm
by epilectrolytics
Yes, here too :(

Re: Wiki broken

Posted: Tue Dec 22, 2020 4:00 pm
by Dade

Re: Wiki broken

Posted: Tue Dec 22, 2020 4:10 pm
by acasta69
It's working fine on my end too.

Re: Wiki broken

Posted: Tue Dec 22, 2020 4:29 pm
by epilectrolytics
Then it might be a problem with german internet providers?
I'm with Unitymedia/Vodafone.
screenshot.png
The good thing is that the Wiki is not broken, I can access it via proxy site.

Re: Wiki broken

Posted: Tue Dec 22, 2020 5:40 pm
by B.Y.O.B.
epilectrolytics wrote: Tue Dec 22, 2020 4:29 pm Then it might be a problem with german internet providers?
Seems likely, if it works fine from other regions and you can access it via proxy.
My internet provider is 1&1.
Let's see if the situation fixes itself in a while.

Re: Wiki broken

Posted: Wed Dec 23, 2020 7:49 am
by CodeHD
Works for me, so not a german-only problem. And there was just another report of it on discord, so it didn't fix itself yet either.

Re: Wiki broken

Posted: Wed Dec 23, 2020 4:55 pm
by mip
Same problem here,
in Montreal
Browser setting French

Re: Wiki broken

Posted: Fri Dec 25, 2020 9:56 pm
by neo2068
It is strange. On Opera, Chrome, Edge and Safari it doesn't work here but on the updated Firefox it started to work again, today. :o :shock:

Re: Wiki broken

Posted: Fri Dec 25, 2020 10:14 pm
by neo2068
In the response header of the https request there are addtional tags for the browsers which doesn't work:

Firefox:

Code: Select all

HTTP/1.1 200 OK
Date: Fri, 25 Dec 2020 22:04:02 GMT
Server: Apache
X-Powered-By: PHP/7.3.23
X-Content-Type-Options: nosniff
Content-language: en
Vary: Accept-Encoding,Cookie,User-Agent
Expires: Fri, 25 Dec 2020 22:04:03 GMT
Cache-Control: private, must-revalidate, max-age=0
Connection: close
Content-Encoding: identity
X-Request-Id: X@Zh0vUctCXiKiQh-bTLRwAAANY
Last-Modified: Fri, 23 Oct 2020 11:01:12 GMT
Content-Encoding: gzip
Content-Length: 5970
Content-Type: text/html; charset=UTF-8
Chrome:

Code: Select all

HTTP/1.1 200 OK
Date: Fri, 25 Dec 2020 22:04:55 GMT
Server: Apache
X-Powered-By: PHP/7.3.23
X-Content-Type-Options: nosniff
Content-language: en
Vary: Accept-Encoding,Cookie,User-Agent
Expires: Fri, 25 Dec 2020 22:04:55 GMT
Cache-Control: private, must-revalidate, max-age=0
Connection: close
Content-Encoding: identity
X-Request-Id: X@ZiB5gMNm@65sG7imY60wAAAFg
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: Fri, 23 Oct 2020 11:01:12 GMT
Content-Encoding: gzip
Content-Length: 5970
Content-Type: text/html; charset=UTF-8
It seems to have to do with apache configuration to use HTTP/2 and the missing support of HTTP/2 for the browsers. :?: The browser should upgrade the connection to HTTP/2 or respond with HTTP/1 to stick to HTTP/1. Strange that only firefox handle it correctly and that after the latest update.