Last modified: 2014-05-16 21:24:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 49154 - Add remaining cookie config variables to JavaScript interface
Add remaining cookie config variables to JavaScript interface
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
All All
: Normal normal (vote)
: 1.24.0 release
Assigned To: Sam Smith
Depends on:
Blocks: 49155 49156
  Show dependency treegraph
Reported: 2013-06-04 20:36 UTC by Matthew Flaschen
Modified: 2014-05-16 21:24 UTC (History)
5 users (show)

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


Description Matthew Flaschen 2013-06-04 20:36:11 UTC
This is necessary to write cookies correctly from JavaScript.  At least one extension (wgCookiePath) is already exporting it for this reason.
Comment 1 Matthew Flaschen 2013-06-04 20:58:03 UTC
We should just add all the remaining cookie variables, except wgCookieHttpOnly, which won't work in JavaScript.  See bug 49156 about providing an easy to use cookie module, which requires this.
Comment 2 Matthew Flaschen 2013-06-04 20:58:51 UTC
Oh, I meant to say, the extension exporting wgCookiePath is MobileFrontend.
Comment 3 Bartosz Dziewoński 2014-05-16 01:32:24 UTC
Was fixed by 7c585b5a33d57469d19e9b176f14b84403488b73 together with bug 49156.
Comment 4 Matthew Flaschen 2014-05-16 21:24:52 UTC
Except wgCookieSecure, due to technical limitations (a combination of how the config variable is modified in place and how the startup module is not protocol-relative); see

Note You need to log in before you can comment on or make changes to this bug.