> On Mar 31, 2015, at 11:39 PM, George wrote:
>
> thanks Sarah
>
> dug deeper and apparently those nginx reported header sites were behind
> Google Pagespeed's service so that must of been why HTTP/2 was reported
That does seem like a likely reason.
.s.
__
thanks Sarah
dug deeper and apparently those nginx reported header sites were behind
Google Pagespeed's service so that must of been why HTTP/2 was reported
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256561,257778#msg-257778
___
nginx ma
It’s awesome to see you all excited about HTTP/2.
We don’t have any test builds (that I know of) in the wild, so I’m not sure
what you’re seeing, George. As we get closer to a release, there *may* be
opportunities for test builds. If you’re interested in that, please send me an
email offlist
Definitely looking forward to Nginx's implementation of HTTP/2 as it's one
of the missing pieces in comparison test with other HTTP/2 enabled web
servers like h2o and OpenLiteSpeed
https://h2ohttp2.centminmod.com/webpagetests1.html :)
Do some folks have access to experimental builds of Nginx with
On 2015-03-17 07:43, Maxim Dounin wrote:
- As previously said, there are no plans to support neither HTTP/2
nor SPDY for upstream connections.
Which of the two will be supported, or will both be supported, and is
there any code in developement we can access to test out and provide
feedback
On Wednesday 18 March 2015 19:11:18 Mark Mielke wrote:
> Hi Valentin:
>
> Are you talking about the same "push" as I am? HTTP/2, or at least SPDY,
> had the ability to *push* content like CSS in advance of the request,
> pushing content into the browsers cache *before* it needs it.
Yes, about tha
Hi Valentin:
Are you talking about the same "push" as I am? HTTP/2, or at least SPDY,
had the ability to *push* content like CSS in advance of the request,
pushing content into the browsers cache *before* it needs it. I'm not
talking about long polling or other technology. I've only read about thi
On Wednesday 18 March 2015 04:32:55 Mark Mielke wrote:
> I think the ability to "push" content,and prioritize requests are examples
> of capabilities that might require intelligence upstream, and therefore a
> requirement to proxy HTTP/2 upstream.
"Server push" doesn't require HTTP/2 for upstream
I think the ability to "push" content, and prioritize requests are examples
of capabilities that might require intelligence upstream, and therefore a
requirement to proxy HTTP/2 upstream. However, I expect much of this is
still theoretical at this point, and until there are actually upstream
server
A CDN was the exact reason i asked the question in the first place, at the
moment not even cloudflare offers spdy or http/2 for upstream servers ( they
use nginx and have spdy enabled ).
Seems to me like http/2 for upstream would make building a CDN / Accelerator
easier(or at least better) for alo
> Am 17.03.2015 um 23:32 schrieb Valentin V. Bartenev :
>
> On Tuesday 17 March 2015 09:49:04 alexandru.eftimie wrote:
>> Will there be support for http/2 for upstream connections? I can't seem to
>> find anything about this online ( either SPDY or HTTP/2 for upstream
>> connections )
>>
>
> Th
On Tuesday 17 March 2015 09:49:04 alexandru.eftimie wrote:
> Will there be support for http/2 for upstream connections? I can't seem to
> find anything about this online ( either SPDY or HTTP/2 for upstream
> connections )
>
The problems that SPDY (and HTTP/2) is trying to solve usually do not
ex
Hello!
On Tue, Mar 17, 2015 at 03:01:09PM +0100, Daniël Mostertman wrote:
> Maxim Dounin schreef op 17-3-2015 om 14:49:
> >Hello!
> >
> >On Tue, Mar 17, 2015 at 09:49:04AM -0400, alexandru.eftimie wrote:
> >
> >>Will there be support for http/2 for upstream connections? I can't seem to
> >>find a
Maxim Dounin schreef op 17-3-2015 om 14:49:
Hello!
On Tue, Mar 17, 2015 at 09:49:04AM -0400, alexandru.eftimie wrote:
Will there be support for http/2 for upstream connections? I can't seem to
find anything about this online ( either SPDY or HTTP/2 for upstream
connections )
No, and there are
Hello!
On Tue, Mar 17, 2015 at 09:49:04AM -0400, alexandru.eftimie wrote:
> Will there be support for http/2 for upstream connections? I can't seem to
> find anything about this online ( either SPDY or HTTP/2 for upstream
> connections )
No, and there are no plans.
--
Maxim Dounin
http://nginx
Will there be support for http/2 for upstream connections? I can't seem to
find anything about this online ( either SPDY or HTTP/2 for upstream
connections )
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256561,257321#msg-257321
___
nginx ma
Indeed. The Wikipedia page covers it quite well FYI -
http://en.wikipedia.org/wiki/HTTP/2
So what is really being asked is for a roadmap for the implementation of
the non-draft differences (i.e HTTP/2.0 allows for non TLS communication,
and multiplexes differently). I am sure nginx will once again
Pedantic, but I object to the wording in the title :) ... SPDY was/is an
experimental branch of HTTP/2, and now that HTTP/2 is in the final stages
of becoming a standard, there is no longer the need for SPDY and hence the
announcement of a deprecation timeline -- it's not and never was SPDY vs.
HTT
Google dumps SPDY in favour of HTTP/2, any plans ore roadmap for HTTP/2 in
nginx?
see
https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html
"HTTP is the fundamental networking protocol that powers the web. The
majority of sites use version 1.1 of HTTP, which was defined in 19
19 matches
Mail list logo
