Page MenuHomePhabricator

Unready
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Aug 22 2016, 8:54 AM (403 w, 5 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Unready [ Global Accounts ]

Recent Activity

Dec 15 2016

Unready added a comment to T153275: URL to pagenames with special characters fail.
Dec 15 2016, 2:26 AM · SRE, Wikimedia-Apache-configuration

Aug 23 2016

Unready added a comment to T135170: Require POST in ?action=purge.

Oops. I saw a bunch of HTML and thought it was the page. Yeah, it's HTML-formatted JSON. My bad.

Aug 23 2016, 10:45 AM · MW-1.28-release (WMF-deploy-2016-08-16_(1.28.0-wmf.15)), MW-1.28-release-notes, MediaWiki-Action-API, Community-Relations-Support, Patch-For-Review, Performance Issue
Unready added a comment to T135170: Require POST in ?action=purge.

Hmmm, why is this task still marked as open/needs triage? Is there anything left to do here?

The API I suppose.

Aug 23 2016, 2:58 AM · MW-1.28-release (WMF-deploy-2016-08-16_(1.28.0-wmf.15)), MW-1.28-release-notes, MediaWiki-Action-API, Community-Relations-Support, Patch-For-Review, Performance Issue

Aug 22 2016

Unready added a comment to T143531: Back out the change that changed action=purge to require a confirmation page.

Going forward, your script (or something like it) should be deployed in Common.js or maybe as a gadget on Wikipedia (etc.) ASAP. It probably would have been better to do that before requiring POST, but here we are now. The screams are only going to get louder.

.... I can submit a patch to core with that script improved to imitate the previous behavior (the exact behavior cannot be achieved since it will have to be done client-side) if someone (from Performance team?) can confirm that it can actually work reliably.

Aug 22 2016, 11:30 PM · MediaWiki-General, Regression
Unready added a comment to T143531: Back out the change that changed action=purge to require a confirmation page.

... Your expectation about GET/POST is also wrong as GET is actually supposed to be retrieving data only not for modifying; ....

Aug 22 2016, 1:02 PM · MediaWiki-General, Regression
Unready added a comment to T143531: Back out the change that changed action=purge to require a confirmation page.

To my understanding, translating GET to POST via JS is not a problem, applying GET directly to the request is, see T135170#2310146

Aug 22 2016, 10:22 AM · MediaWiki-General, Regression
Unready added a comment to T143531: Back out the change that changed action=purge to require a confirmation page.

Two questions ...

  1. Is there any point to the "purge" right now?
  2. Is requiring POST the first step toward requiring a token?
Aug 22 2016, 9:35 AM · MediaWiki-General, Regression