new post form does not work on chrome

ID:2431460
 
Mar 5 2019, 4:36 pm
BYOND Version:N/A (Website Bug)
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 72.0.3626.109
Applies to:Website
Status: Open
Issue hasn't been assigned a status value.
Descriptive Problem Summary:
The "new post" form does not work on chrome - it simply returns you to the forum main page

Numbered Steps to Reproduce Problem:
1. try to create a new post (such as this bug report)
2. press submit
3. ree it didnt work

Code Snippet (if applicable) to Reproduce Problem:


Expected Results:
making a post

Actual Results:
it just sends you to the front page of the forum

Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?

When does the problem NOT occur?


Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Workarounds:
right click
inspect element
find <form action="http://www.byond.com/forum/" name="post_form_1" method="post" ...>
replace the thing to say action="https://secure.byond.com/forum/"
then press submit
I had to use this workaround while submitting this bug report
Mar 5 2019, 4:44 pm
While I'm here I would just like to say that it's really fucking stupid to have https be on a separate domain from http.
Mar 5 2019, 8:53 pm
The problem is with HTTPS Everywhere, not Chrome.

The separate domain thing is because the secure subdomain was only ever intended to be used for logins and such, basically only sensitive stuff.

I was talking to MrStonedOne about this recently. The problem here is, it's a massive pain in the butt to fix this so that there's an https www subdomain and also still a secure subdomain. I have to reconfigure a number of things way under the hood on the server, plus make changes to the site. It's not impossible but it's way outside of what I'm working on right now.

But be assured I'm not punting this forever. I know this is an increasing annoyance for some users so I'll have to get to it. For now I would suggest as a workaround putting byond.com in an exception list for HTTPS Everywhere.