Get it, I'll try it, thank you again.
On Thu, Jul 12, 2018 at 1:02 AM Maxim Dounin wrote:
> Hello!
>
> On Wed, Jul 11, 2018 at 08:56:56PM +0800, 洪志道 wrote:
>
> > But there are still some clients use the old version.
> > Is it a way to be compatible with it?
> > Or other suggestions?
> > @Maxim
Hello!
On Wed, Jul 11, 2018 at 08:56:56PM +0800, 洪志道 wrote:
> But there are still some clients use the old version.
> Is it a way to be compatible with it?
> Or other suggestions?
> @Maxim Dounin
As I already wrote in ticket #1397, we can try introducing a
workaround in nginx, but I'm not
Thank you.
But there are still some clients use the old version.
Is it a way to be compatible with it?
Or other suggestions?
@Maxim Dounin
On Wed, Jul 11, 2018 at 5:43 PM tokers wrote:
> Hello!
>
> There is a known issue caused by some obsolete client like old version
> okhttp (incomplete
Hello!
There is a known issue caused by some obsolete client like old version
okhttp (incomplete protocol implements).
Here is the ticket: https://trac.nginx.org/nginx/ticket/1397.
___
nginx-devel mailing list
nginx-devel@nginx.org
BTW. It works well by the temporary fix.
--- a/src/http/v2/ngx_http_v2_filter_module.c
+++ b/src/http/v2/ngx_http_v2_filter_module.c
@@ -446,7 +446,6 @@ ngx_http_v2_header_filter(ngx_http_request_t *r)
if (h2c->table_update) {
ngx_log_debug0(NGX_LOG_DEBUG_HTTP, fc->log, 0,
