-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Hello!

On 01/10/18 19.32, Maxim Dounin wrote:
> Hello!
>
> On Sat, Sep 29, 2018 at 08:29:56AM +0700, Dewangga Alam wrote:
>
>> Currently, I am using nginx-1.8.1 in production. And I need SPDY to
>> works on nginx-1.14.0 co-exists with http/2. Because I still need SPD
Y
>> for compatibility, and for future deployment, I will migrate it all t
o
>> HTTP/2.
>>
>> To make this possible, so I was create patch to make SPDY and HTTP/2
run
>> together.
>>
>> I was read cloudflare patch regarding this issue (spdy & http/2) and
>> make some adjustment (patch attached).
>>
>> But, got some errors when compiling. The error message was :
>
> [...]
>
> Just to make sure you understand it:
>
> As per https://caniuse.com/#search=spdy - SPDY is only supported by
> about 20% of browsers in use, and most of these browsers already
> support HTTP/2. Most modern browsers do not have SPDY support.
>
> In contrast, HTTP/2 is supported by more than 80% of browsers in
> use. And most modern browsers which do not support HTTP/2 - do
> not support SPDY either.
>
> Moreover, SPDY code you are trying to bring back is not maintained
> for a long time now, since it was replaced by HTTP/2 in nginx
> 1.9.5. And there are various known problems fixed in the HTTP/2
> code since then, so likely there are similar problems in the SPDY
> code.
>
> Summing the above, trying to bring back SPDY support is mostly
> meaningless and might be dangerous. It might be a better idea to
> focus on migrating to HTTP/2 instead.
>

Many thanks for very clear explanation, Maxim. We will focus on
migrating to HTTP/2.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEZpxiw/Jg6pEte5xQ5X/SIKAozXAFAluyR8YACgkQ5X/SIKAo
zXCFWg/+OOCivq1wL4iNhf3yrpfnMfvzottON1kuu1tR8FCZoO2/rls59eVWOBmE
7I3QjfYQ0CPM7w7n0iB83Em93gCnvWXY/djX2PVoi++o6Vy9ISNlqGCXxBVwneDx
p3yNJm+uzvzHisNYTHRc2vnwXCq4fa4eoVxrnm8v7I/VD8F6D2SdCZ5HwM+qZW09
fdbwLwGeBRjbZIVFlXU3lZcpRPUs+42of2dqtUIzGs1qLPotgYVW7HnV2ULnBaqo
IMK22kMs7kecnd3WLgTG2uu6n0abcf1UNG0QbYMWwzuyh/W6K61lGXC54pRI1/Xy
BtTiWzE1XQP7BabALO5BbhpKz7WcpRFGN+405j7E0s8/ZwhylwwISoN2jaEg+zmZ
1C4Kv/fdFD96s1IPtuXy1IhXYg3OwBI9nNkaDSSNR4ipNhg7uTlMR/6eMFFWlaCW
twc/FbR0GG7UoafwiKuZuNRuZBbjPALn2WVv+FSamaDYzrwR7PnTsB2/D8Rzc62D
u28Za09k4pCL36GQ5mjL4i+NoO8gxENm+e43GaMPRnWn8h3d1nDtJoODvPol8YBk
zR4Wef2PrzzYmPdEDMhS2SSmuIA0aMyTzWeRiMJFXeD8QRs31Q1dXu86sJKkiyS9
QK3G/qpYsxy1ze+aXKF3n/a0hd3KDT8Iaa39Lzgmyb2tWtFaE4Y=
=kt7/
-----END PGP SIGNATURE-----
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel