Forum: NGINX Issue with HTTP/2 and async file upload from Safari on iOS

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
De7b680154f831d87d8ea48743852f14?d=identicon&s=25 ZaneCEO (Guest)
on 2016-06-05 01:17
(Received via mailing list)
Hi guys,
I'm at my first deploy of Nginx with php-fpm after 10+ years of love
with
Apache and mod_php. So far so (very) good.

I just have a peculiar issue with Safari on iOS. As you can read here
http://stackoverflow.com/questions/37635277/safari...
, my webapp allows the user to select an image, client-resize it via JS
and
then upload it via jQuery.

The problem is that Safari on iOS 9 sometimes fails the upload with the
error

POST <my upload url>, Could not connect to the server.

I just found out that  when I disabled the HTTP/2 form my server config
the
issue vanishes.

Is this a known issue somehow? Is there any other solution that doesn't
require me to go nuclear on HTTP/2?

Thanks for your help!

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267385,267385#msg-267385
9c50ac7dd6daee206e621bddce7b8877?d=identicon&s=25 Lucas Rolff (Guest)
on 2016-06-05 01:31
(Received via mailing list)
De7b680154f831d87d8ea48743852f14?d=identicon&s=25 ZaneCEO (Guest)
on 2016-06-06 09:54
(Received via mailing list)
Thank you very much!! At least now I know what's going on! Let's wait
for a
patch...

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267385,267408#msg-267408
419b29425e1245886d653616ba381f00?d=identicon&s=25 Maxim Konovalov (Guest)
on 2016-06-06 10:01
(Received via mailing list)
On 6/6/16 10:53 AM, ZaneCEO wrote:
> Thank you very much!! At least now I know what's going on! Let's wait for a
> patch...
>
It was fixed in 1.11.0 two weeks ago.

--
Maxim Konovalov
Fd3206619c7f3ae986e24c03fa1ae0a7?d=identicon&s=25 A. Schulze (Guest)
on 2016-06-06 12:01
(Received via mailing list)
Hello,

I'm using horde and observe similar errors since some weeks.
Unsure if the same problem would be the reason.

Maxim Konovalov:
> It was fixed in 1.11.0 two weeks ago.

I found one patch 'preread_buffer.patch" attachtd to
https://trac.nginx.org/nginx/ticket/959
That patch looks not trivial (to me)
Would it be possible to publish a version for nginx-1.10.1, too

I would try if that solve the errors I observe.

Thanks
Andreas
419b29425e1245886d653616ba381f00?d=identicon&s=25 Maxim Konovalov (Guest)
on 2016-06-06 12:05
(Received via mailing list)
On 6/6/16 1:00 PM, A. Schulze wrote:
> https://trac.nginx.org/nginx/ticket/959
> That patch looks not trivial (to me)
> Would it be possible to publish a version for nginx-1.10.1, too
>
> I would try if that solve the errors I observe.
>
Why don't you just try 1.11.1?

The code difference between it and 1.10.1 (already released a week
ago) is marginal.

--
Maxim Konovalov
1266aa99d1601b47bbd3ec22affbb81c?d=identicon&s=25 B.R. (Guest)
on 2016-06-06 20:21
(Received via mailing list)
The problem is, if (s)he is using the official packages, he will get the
updates of the mainline channel, thus differing more and more from the
stable channel which is supposed to be cheaper on features but with
usable
ones.

My 2 cents,
---
*B. R.*
De7b680154f831d87d8ea48743852f14?d=identicon&s=25 ZaneCEO (Guest)
on 2016-07-08 23:55
(Received via mailing list)
Hi guys,
that's the issue for me: I'm with Ubuntu 16.04 official packages. I apt
dist-upgrade, but still I'm on nginx/1.10.0..

Any solution other than switching to
https://launchpad.net/~nginx/+archive/ubuntu/development (wich scares
the
skull out of me, since this is a production server)?

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267385,268204#msg-268204
De7b680154f831d87d8ea48743852f14?d=identicon&s=25 itpp2012 (Guest)
on 2016-07-09 00:35
(Received via mailing list)
You can manually apply the patches and recompile.

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267385,268205#msg-268205
63f341734581b167c7b698169bdd2510?d=identicon&s=25 Lukas Tribus (Guest)
on 2016-07-09 12:26
(Received via mailing list)
> Any solution other than switching to
> https://launchpad.net/~nginx/+archive/ubuntu/development (wich scares the
> skull out of me, since this is a production server)?

Use nginx provided binaries if compiling from source is not an option:
http://nginx.org/en/linux_packages.html#mainline
De7b680154f831d87d8ea48743852f14?d=identicon&s=25 ZaneCEO (Guest)
on 2016-07-11 10:25
(Received via mailing list)
@itpp2012 : building from source is a no-go for me due to future upgrade
concerns

@Lukas : will follow your suggestion and try the ngingx-provided bins,
thanks!

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267385,268236#msg-268236
1b8822738bf9c82ce71ca9e836191ea8?d=identicon&s=25 Jason Woods (Guest)
on 2016-07-15 14:09
(Received via mailing list)
> On 11 Jul 2016, at 09:25, ZaneCEO <nginx-forum@forum.nginx.org> wrote:
>
> @itpp2012 : building from source is a no-go for me due to future upgrade
> concerns
>
> @Lukas : will follow your suggestion and try the ngingx-provided bins,
> thanks!

I’m beginning to hear many reports now of Safari and iOS users hitting
connection issues on several websites, not just around upload but any
arbitrary POST it seems.
Building from source is a no go too, and we’ve always stayed on the
feature stable branch as it’s easier to maintain since we don’t need to
worry about additional features causing issues.

I was anticipating such a compatibility problem to be fixed in feature
stable but so far it’s looking like we will have to bite the bullet and
move to mainline.
Would I be correct here? It seems for our case at least, feature stable
HTTP2 is not stable for production use at this time.

Jason
63f341734581b167c7b698169bdd2510?d=identicon&s=25 Lukas Tribus (Guest)
on 2016-07-15 14:26
(Received via mailing list)
> I was anticipating such a compatibility problem to be fixed in feature stable
but so far its looking like we will have to bite the bullet and move to 
mainline.
> Would I be correct here? It seems for our case at least, feature stable HTTP2 is
not stable for production use at this time.

Correct. It has been stated multiple times that mainline is the
suggested branch for HTTP2 use and that statement is still true.

So yes, do not use the stable branch if using HTTP2.



Lukas
This topic is locked and can not be replied to.