Last modified: 2013-10-09 17:23:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44286, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 42286 - API and audience
API and audience
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-11-20 11:14 UTC by jeblad
Modified: 2013-10-09 17:23 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description jeblad 2012-11-20 11:14:57 UTC 
The API should enforce audience public for all requests that are GET, not "must revalidate" and "maxage" or "smaxage". Otherwise the request is private.

To make it somewhat simpler we could say that GET is public and POST is private, and if "maxage" or "smaxage" is set then it is always public.

The reason for this is caching that may leak information.
Comment 1 Lydia Pintscher 2013-10-08 22:35:38 UTC 
Adam: Can you please say what we should do with this?
Comment 2 Addshore 2013-10-09 09:35:17 UTC 
GET is public and POST is private (get requirement is read post requirement  is write) so this is done everywhere


Not sure about the "maxage" or "smaxage"
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links