Forum > Other

Show unread not showing unread

<< < (4/5) > >>

440bx:

--- Quote from: Martin_fr on January 08, 2022, 10:49:19 am ---Btw, the source of smf can be downloaded. So it can be found out how it works....

--- End quote ---
I figured that if I see "<anything> unread" anywhere on the page, I'll just click on it.  That's my "theory" :)

GetMem:
@440bx

It most likely related to your connection quality. If you login, then access the "Show unread" section, then go for a 15 minutes walk and your session expires, the unread messages magically are gone. Most likely a software bug. My theory is that after login you get disconnected for a short period of time. The question is: do you have problem with the connection?   

440bx:
Hi Getmem,

I've been having problems with the connection but only with the Lazarus forum.  Every time I'm away for more than a few minutes then I get a timeout, sometimes even two before I finally get to see a page again.

That only happens with the Lazarus forums.  With any other website the response is quick.  I posted a question a few days ago to find out if other people were experiencing that problem (the timeouts) and, it seems it's only happening to me.

One thing that might be involved in all the "quirks" I am experiencing is that Chrome says it's not connected using https (just http), there is that red "Not secure" label next to the Lazarus forum url.

That problem started about a month ago, maybe a bit more and, I switched to Firefox which didn't complain about the Lazarus certificate.  Unfortunately, Firefox, a couple of weeks ago couldn't start anymore and, even reinstalling the thing didn't solve the problem.  Because of that, I switched back to Chrome which, for some reason, is unhappy with the Lazarus site certificate.

It's quite possible that the quirks I'm experiencing are due to Chrome being unhappy about the certificate causing it to operate differently than it normally would.

I should probably move the stuff I've accumulated in this VM to another - fresh - VM.  Doing that would probably make Firefox happy which has no complaints about Lazarus web certificate.  I'll eventually run out of patience and do that... <chuckle>






Martin_fr:

--- Quote from: 440bx on January 08, 2022, 01:30:22 pm ---I've been having problems with the connection but only with the Lazarus forum.  Every time I'm away for more than a few minutes then I get a timeout, sometimes even two before I finally get to see a page again.

--- End quote ---
We are aware that there are a lot of small-ish delays (5 - 15 secs), and occasional bigger delays.
The cause has not yet been established.


--- Quote ---One thing that might be involved in all the "quirks" I am experiencing is that Chrome says it's not connected using https (just http), there is that red "Not secure" label next to the Lazarus forum url.

--- End quote ---
For me both Chrome and Firefox have no problem with the certificate, or any https related issue. (Win 10 64 bit)

trev:
@440BX: Many browser certificate issues recently have been due to the Let's Encrypt root certificate (DST Root CA X3) expiry on 30 September. This caused a couple of issues:

1) Unless your OS and/or browser root certificate store was updated (Firefox's was), any Let's Encrypt server certificate fails verification because of the root certificate expiry.

2) As part of a kludge for Android  devices that are not updated and cannot be updated, Let's Encrypt's new root certificate (ISRG Root X1) is also “cross-signed” by their now expired root certificate and some programs (eg FreeBSD's fetch utility) don't like it because one of the certification paths looks like:


--- Code: Text  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---1       Sent by server  sentry.orgFingerprint SHA256: 4676efa667a14502b8e2d987f5e66f4f7c1836c3785ad80ad2e0df859df85890Pin SHA256: NjaOyokcU74v2JTF2iANx0flEzwfhOaUOsSJ72WHBVU=RSA 2048 bits (e 65537) / SHA256withRSA2       Sent by server  R3Fingerprint SHA256: 67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfdPin SHA256: jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0=RSA 2048 bits (e 65537) / SHA256withRSA3       Sent by server  ISRG Root X1Fingerprint SHA256: 6d99fb265eb1c5b3744765fcbc648f3cd8e1bffafdc4c2f99b9d47cf7ff1c24fPin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=RSA 4096 bits (e 65537) / SHA256withRSA4       In trust store  DST Root CA X3   Self-signed    Fingerprint SHA256: 0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739Pin SHA256: Vjs8r4z+80wjNcr1YKepWQboSIRi63WsWXhIMN+eWys=RSA 2048 bits (e 65537) / SHA1withRSAValid until: Thu, 30 Sep 2021 14:01:15 UTCEXPIREDWeak or insecure signature, but no impact on root certificate

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version