https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #34 from Jan Zerebecki ---
I don't think there is anything directly blocking SPDY except upgrading nginx
(or switching to something else) and testing it. Both are quite a bit of work
in themselves. After that it will be usefull to a
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #33 from Nemo ---
https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Backlog#SPDY_.2F_HTTP_2.0
is empty as well and all https://www.mediawiki.org/?oldid=975972 says is "Would
help with asset delivery, front-end perf".
--
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #32 from MZMcBride ---
(In reply to Faidon Liambotis from comment #26)
> There's a lot of work involved, some of which is documented under
> https://wikitech.wikimedia.org/wiki/HTTPS/Future_work and other that is not
> (SPDY).
>
>
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Jan Zerebecki changed:
What|Removed |Added
CC||jan.wikime...@zerebecki.de
Co
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #31 from Faidon Liambotis ---
That's good news indeed.
Of course that 67% figure is bogus, as it assumes SPDY is one protocol, while
there are four versions available and browsers & servers each support a
different combination of t
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #30 from Gabriel Wicke ---
Good news: The last browser hold-out (Safari) will finally get SPDY support as
well:
"Safari supports the latest web standards, including WebGL and SPDY"
http://www.apple.com/pr/library/2014/06/02Apple-An
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #29 from Gabriel Wicke ---
nginx 1.6 now has SPDY 3.1 support.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #28 from Gabriel Wicke ---
Another bit of info re keep-alives from
https://groups.google.com/forum/#!topic/spdy-dev/xgyPztsAKls:
FF keeps SPDY connections alive for 3 minutes using PING frames. Servers can
also keep connections al
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #27 from Gabriel Wicke ---
@Faidon: I agree that a wider discussion is needed to come to a conclusion &
make a plan / agree on priorities. Lets use this bug to collect more
information for now to inform that discussion.
Nginx lets
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Nemo changed:
What|Removed |Added
Blocks||27946
--
You are receiving this mail because:
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #26 from Faidon Liambotis ---
Let's take a step back: SSL's scaling & performance requirements and SPDY are
not things that can be discussed effectively in a BZ bug, I think. There's a
lot of work involved, some of which is document
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #25 from Gabriel Wicke ---
(In reply to Ryan Lane from comment #24)
> If the connection is broken and a new connection is needed, it'll likely hit
> another server when using round robin, which means an SSL cache miss. This
> is pre
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #24 from Ryan Lane ---
(In reply to Gabriel Wicke from comment #23)
> (In reply to Ryan Lane from comment #22)
> > (In reply to Gabriel Wicke from comment #21)
> > > > Can you use a shared SSL cache?
> > >
> > > Can you describe w
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #23 from Gabriel Wicke ---
(In reply to Ryan Lane from comment #22)
> (In reply to Gabriel Wicke from comment #21)
> > > Can you use a shared SSL cache?
> >
> > Can you describe what this is about?
> >
>
> Sure. Currently we use
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
jeremyb changed:
What|Removed |Added
See Also||https://bugzilla.wikimedia.
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #22 from Ryan Lane ---
(In reply to Gabriel Wicke from comment #21)
> So I guess this is waiting for a more up to date version of nginx at this
> point.
>
> (In reply to Ryan Lane from comment #16)
> > > Yeah -- the packaged build
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #21 from Gabriel Wicke ---
So I guess this is waiting for a more up to date version of nginx at this
point.
(In reply to Ryan Lane from comment #16)
> > Yeah -- the packaged build of Nginx that we are running in production was
> >
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Roan Kattouw changed:
What|Removed |Added
CC||roan.katt...@gmail.com
--- Comment #20
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #19 from Gabriel Wicke ---
@Ryan: My response directed to Faidon was really for you, in case that wasn't
clear from the context.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #18 from Gabriel Wicke ---
@Ori, ah, I see. I guess a backport or the next Ubuntu LTS upgrade (three
months from now?) could help here.
@Faidon: Is the main complication becoming tied to nginx? With SPDY being an
application-level
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #17 from Roan Kattouw ---
(In reply to comment #15)
> Yeah -- the packaged build of Nginx that we are running in production was not
> compiled with the requisite flag for SPDY support. But your broader point is
> correct: it is pret
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #16 from Ryan Lane ---
(In reply to comment #15)
> (In reply to comment #14)
> > Are there specific issues that prevent us from applying the simple config
> > change in [1] for a subset of the production traffic for testing?
> >
>
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #15 from Ori Livneh ---
(In reply to comment #14)
> Are there specific issues that prevent us from applying the simple config
> change in [1] for a subset of the production traffic for testing?
>
> [1]:
> https://gerrit.wikimedia.o
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #14 from Gabriel Wicke ---
SPDY is an optimization that a lot of our clients can profit from now:
http://caniuse.com/spdy
Especially clients on high-latency and low-bandwidth links (mobile, developing
countries) benefit from header
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Ori Livneh changed:
What|Removed |Added
Keywords||performance
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #13 from Yuvi Panda ---
That patch has been merged, and dynamicproxy has spdy enabled! \o/
http://spdycheck.org/#pinklake.wmflabs.org
This provides support for spdy/2, which is what nginx supports so far. It is a
newer build of ng
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #12 from Yuvi Panda ---
https://gerrit.wikimedia.org/r/#/c/87682/ enables this for the labs
dynamicproxy.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
__
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Gabriel Wicke changed:
What|Removed |Added
Priority|Lowest |Normal
--- Comment #11 from Gabriel Wi
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Yuvi Panda changed:
What|Removed |Added
CC||yuvipa...@gmail.com
--- Comment #9 from Y
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #10 from Gabriel Wicke ---
From bug 33890:
SPDY is supported in Nginx and most modern browsers. Since we are using Nginx
for HTTPS termination already, we should consider enabling SPDY support in it.
This cuts down the overhead per
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Gabriel Wicke changed:
What|Removed |Added
CC||gwi...@wikimedia.org
--- Comment #8 fr
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Marco changed:
What|Removed |Added
CC||maic...@yahoo.com
--- Comment #7 from Marco -
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Nemo changed:
What|Removed |Added
CC||federicol...@tiscali.it
Component|Site
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Antoine "hashar" Musso changed:
What|Removed |Added
Priority|Normal |Lowest
--- Comment #6 from An
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Platonides changed:
What|Removed |Added
CC||platoni...@gmail.com
--- Comment #5 from
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #4 from Leslie Carr 2012-04-17 21:11:34 UTC
---
They just released an apache mod for this...
http://googledevelopers.blogspot.com/2012/04/add-spdy-support-to-your-apache-server.html
Might be worth testing out in labs, however it l
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #3 from Brion Vibber 2012-01-25 18:10:29 UTC
---
I'm seeing surprisingly little user-facing documentation on this. :P
Last section of https://code.google.com/p/mod-spdy/wiki/GettingStarted seems to
indicate that users should use h
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
Sam Reed (reedy) changed:
What|Removed |Added
Priority|Unprioritized |Normal
Severity|minor
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
p858snake changed:
What|Removed |Added
CC||p858sn...@gmail.com
--- Comment #2 from p8
https://bugzilla.wikimedia.org/show_bug.cgi?id=33890
--- Comment #1 from Brion Vibber 2012-01-22 22:26:57 UTC
---
Firefox 11 should include spdy, though i think disabled by default.
Some dumb questions:
* does this require using alternate URLs to access resources, eg
spdy://en.wikipedia.org/ ?
40 matches
Mail list logo
