Closed Glorfindel83 closed 7 years ago
If the browser uses the GET
method, it could render https://metasmoke.erwaysoftware.com/post/59564 and show a confirmation popup.
That's a POST route; hitting it with GET will 404. Does this happen when you click the link from the post page?
Yes it does.
Sent from my iPhone (and therefore likely to contain typing errors)
On 11 Mar 2017, at 22:51, ArtOfCode notifications@github.com wrote:
That's a POST route; hitting it with GET will 404. Does this happen when you click the link from the post page?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
What browser?
@Undo1 This happens to me in the latest version of Safari.
Interesting, norepro in 10.1 for me.
Here's a screenshot (I'm on my phone at the moment):
It says something about verify_developer; could it happen to me since I'm not a dev?
From Jonathan
On Mar 13, 2017, at 8:50 PM, Parker Erway notifications@github.com wrote:
Interesting, norepro in 10.1 for me.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@NobodyNada that didn't come through by the looks of it, could you re-upload the image when you get to a computer?
Screenshot uploaded; sorry I forgot. GitHub doesn't want to display it for some reason; you'll have to click the link.
The spam flag which is sometimes visible in a report leads to a 404, e.g. https://metasmoke.erwaysoftware.com/post/59564/spam_flag
According to the discussion following this chat message, it's because of a wrong HTTP verb.
Also reported by QPaysTaxes.