Hello,
I have a weird problem that suddenly appeared on a client's website
yesterday. We have a redirection from non www to www and sometimes the
redirection sends somewhere else:
[root@genious33 nginx-1.11.2]# curl -IL -H "host: hespress.com" x.x.x.x
HTTP/1.1 301 Moved Permanently
Server: ng
The error I am getting in the logs:
"upstream prematurely closed connection while reading response header from
upstream"
After the first request it works for 10-15 seconds without any problem.
According to tcpdump in the first request (the failing one) the upstream is
receiving one GET and nothi
> 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.
> On 11 Jul 2016, at 09:25, ZaneCEO 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
connec
Server:
Linux CentOS 6.(x)
NGINX with RTMP module enabled (compiled myself using an online tutorial)
I use FFmpeg to stream to this server, and one stream works perfectly.
Example of perfectly working stream from IP camera:
ffmpeg -loglevel verbose -rtsp_transport tcp -i rtsp://admin:ad
