When the font issue was happening I actually looked at the "View Page Info" screen in FF and noticed it said "Render mode: Quirks", said hmm to myself, but didn't think more of it. Now the render mode is "Standards compliance mode" which does sound a whole lot more reassuring.
In fact, this is caused by the content type header of the server response not being set correctly and the nbsp;'s used for invisible anchors get interpreted as latin1 instead of utf8. The root cause seems to be a flawed mod_cache module in conjunction with some backend requests temporarily failing via VPN.
Update: the server status pages are not being proxied anymore, which didn't make much sense anyway. If my theory about the buggy mod_cache module is correct you should now always get those pages with the correct encoding (UTF-8) set in the HTTP response headers which will lead to correctly rendered pages. So far I couldn't reproduce the issue anymore, despite the server-side cache being enabled again.
Please let us know if that's not the case for you.
Well, I don't know should I introduce this here or somewhere else. Please, just move this message where it should be if I missed.
1) I open a "Message board" link in front page and see that last message (for me I guess) in the news thread is 14 days old. Then I click it and... I see that the last message is 31 days old. Reloading page, resorting with "Newest reply first" doesn't help. No proxies, no caches on my side.
2) Sorting doesn't work as it should. In technical news I see threads with 1269 days from the last reply and only after that I see threads with 28 days from last reply. Looks like it sorts threads not by last message date+time, but as a text field in alphabet order (string "1269" in text sorting will be above "28").
The threads down to 1269 days are 'sticky' - pinned to the top of the list by moderators or administrators. Maybe it's time for a review whether all of them still need that status.
Well, there is a bright side.
)
Well, there is a bright side. I can now see your site without my glasses.
Sorry, not anymore... ;-)
)
Sorry, not anymore... ;-)
Einstein@Home Project
RE: That put the pages into
)
When the font issue was happening I actually looked at the "View Page Info" screen in FF and noticed it said "Render mode: Quirks", said hmm to myself, but didn't think more of it. Now the render mode is "Standards compliance mode" which does sound a whole lot more reassuring.
RE: In fact, this is caused
)
Update: the server status pages are not being proxied anymore, which didn't make much sense anyway. If my theory about the buggy mod_cache module is correct you should now always get those pages with the correct encoding (UTF-8) set in the HTTP response headers which will lead to correctly rendered pages. So far I couldn't reproduce the issue anymore, despite the server-side cache being enabled again.
Please let us know if that's not the case for you.
Best,
Oliver
Einstein@Home Project
Well, I don't know should I
)
Well, I don't know should I introduce this here or somewhere else. Please, just move this message where it should be if I missed.
1) I open a "Message board" link in front page and see that last message (for me I guess) in the news thread is 14 days old. Then I click it and... I see that the last message is 31 days old. Reloading page, resorting with "Newest reply first" doesn't help. No proxies, no caches on my side.
2) Sorting doesn't work as it should. In technical news I see threads with 1269 days from the last reply and only after that I see threads with 28 days from last reply. Looks like it sorts threads not by last message date+time, but as a text field in alphabet order (string "1269" in text sorting will be above "28").
The threads down to 1269 days
)
The threads down to 1269 days are 'sticky' - pinned to the top of the list by moderators or administrators. Maybe it's time for a review whether all of them still need that status.