On 02/02/2013 05:30 PM, Finne Boonen wrote:
I grabbed community/BOF room 1 (h3227) tomorrow @ 12h for a meetup
Great! I will be there.
Thank you very much for arranging this!
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
If you want to differentiate categories of API requests in logs, add
descriptive noop query params to the requests. I.e mfmode=2. Doing this in
request headers and altering edge config is unnecessary and a bad design
pattern. On the analytics side, if parsing query params seems challenging
vs.
the reason to use two fields instead of one makes it much easier to
implement or performant?
On Sun, Feb 3, 2013 at 1:08 AM, David Schoonover d...@wikimedia.org wrote:
Huh! News to me as well. I definitely agree with that decision. Thanks, Ori!
I've already written the Varnish code for setting
Regarding varnish cacheability of mobile API requests with a logging query
param - it would probably be worth making frontend varnishes strip out all
occurrences of that query param and its value from their backend requests
so they're all the same to the caching instances. A generic param name
Considering that the query component of a URI is meant to identify the
resource whereas HTTP headers are meant to tell the server additional
information about the request, I think a header approach is much more
appropriate than a no-op query parameter.
If the X- is removed, I'd have no problem
That's not at all true in the real world. Look at the actual requests for
google analytics on a high percentage of sites, etc.
Setting new request headers for mobile that map to new inflexible fields in
the log stream that must be set on all non mobile requests (\t-\t-)
equals gigabytes of
Finne - you're awesome! Thank you for setting up the BoF - it was a good
meetup :-)
-Alolita
On Sun, Feb 3, 2013 at 9:07 AM, Quim Gil q...@wikimedia.org wrote:
On 02/02/2013 05:30 PM, Finne Boonen wrote:
I grabbed community/BOF room 1 (h3227) tomorrow @ 12h for a meetup
Great! I will be
Remind me again why a production setup is logging every header of every
request? Also, if you are logging every header, then the amount of data
added by a single extra header would be insignificant compared to the rest
of the request.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of
On Fri, Jan 25, 2013 at 12:51 PM, Diederik van Liere
dvanli...@wikimedia.org wrote:
No, the output format of http://dumps.wikimedia.org/other/pagecounts-raw/
will stay the same.
It seems that page names are coming through with spaces now, where
they didn't before. See
On 03.02.2013, 2:02 Brion wrote:
On Feb 2, 2013 1:45 PM, Platonides platoni...@gmail.com wrote:
Your system does not seem to support OGG audio format. Downloading this
file without ogg support may need a significant amount of space and
bandwith. Downloading article.wav ... 20%
Something
It was great to see all of you! :)
Željko
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Sunday, February 3, 2013, Tyler Romeo wrote:
Remind me again why a production setup is logging every header of every
request?
That's ludicrous. Please reread our udplog format documentation and this
entire thread carefully, especially the first message before commenting any
further.
MediaWiki Bugzilla Report for January 28, 2013 - February 04, 2013
Status changes this week
Bugs NEW : 407
Bugs ASSIGNED : 82
Bugs REOPENED : 40
Bugs RESOLVED
13 matches
Mail list logo
