Bug 24067 – forum.dlang.org: HTML refresh; NNTP connection error: Connection closed

I tried to post a reply to a post and received Posting status Validating... nothing happened. When I aktivated the refresh HTML feature (why is that necessary? Common practice it that the server responds with a HTTP redirect!) I got back to the editor and a dotted red box containing NNTP connection error: Connection closed appears. Additional question: How do I in the future report forum errors after issues.dlang.org will have been put into read-only mode and under the assumption that I will not own a github account?

(In reply to kdevel from comment #0) > I tried to post a reply to a post and received Sent an email to the NNTP server admin. > When I aktivated the refresh HTML feature (why is that > necessary? Common practice it that the server responds with a HTTP > redirect!) You can't put a timeout on a location redirect (3xx). I could move the http-equiv tag into a header if that would improve things for you? > Additional question: How do I in the future report forum errors after > issues.dlang.org will have been put into read-only mode and under the > assumption that I will not own a github account? - Email (Mike, Walter, maybe any other @dlang.org address you can find) - Slack - Discord - IRC - Matrix (bridged to Discord) Someone on any of these should be able to reach someone who can do something about the problem.

(In reply to Vladimir Panteleev from comment #1) > [...] > You can't put a timeout on a location redirect (3xx). After the POST request is finshed the post is not yet available? Why not tell the user that their post was only queued? > I could move the > http-equiv tag into a header if that would improve things for you? No. > [...] > Someone on any of these should be able to reach someone who can do something > about the problem. The present issue is rated "P1 critical" but except for your response it looks as if there is no progress for > 72 h. No notice on dlang.org or on the forum page. Do you need additional computational/personal resources? [BTW: Is that new that bugzilla inserts a blank line after quoted text?]

(In reply to kdevel from comment #2) > (In reply to Vladimir Panteleev from comment #1) > > [...] > > You can't put a timeout on a location redirect (3xx). > After the POST request is finshed the post is not yet available? Why not > tell the user that their post was only queued? It's kind of mentioned on https://forum.dlang.org/help , but usually it's an implementation detail that users don't need to worry about. > The present issue is rated "P1 critical" but except for your response it > looks as if there is no progress for > 72 h. No notice on dlang.org or on > the forum page. I don't know anything other than that Walter Bright has been informed of the situation, and at least two attempts have been made to reach the person running the NNTP server. > Do you need additional computational/personal resources? I think we actually do. The plan to move infrastructure under DLF control has been around for a while, but someone needs to take the time to write a proposal and work on an actual implementation plan and implementation which covers the pertinent aspects, such as backups / redundancy / GDPR compliance etc.

*** Issue 24068 has been marked as a duplicate of this issue. ***

I added a banner to forum.dlang.org pointing towards this issue.

The server is back up!