Hi,
I'm trying to implement live image resizing on nginx using
ngx_http_image_filter_module, and I get some weird issues with it.
this is my config for resizing:
server {
listen ;
server_name localhost;
set $backend 'bucket.s3.amazonaws.com';
resolver 8.8.8.8;
resolver_timeout
B.R.
> I am curious: apart from a training prospective at code digging, what was
the goal?
> In other words, where did you expect the IP address to come from, if not
from a system network socket?
We have NGINX AWS EC2 Instances behind AWS EC2 ELBs, as well as Fastly's
CDN and maybe some custom loa
Hello!
On Mon, Feb 06, 2017 at 12:43:24PM +0200, ST wrote:
> I have two mp4 files served by nginx: A ( https://goo.gl/lYGXjC ) and B
> ( https://goo.gl/ZsnX7M ). File A starts pretty fast ca. 2s and it
> buffers/caches "future" content, however to B it takes more than 6s and
> it doesn't seem to
Hello,
I have two mp4 files served by nginx: A ( https://goo.gl/lYGXjC ) and B
( https://goo.gl/ZsnX7M ). File A starts pretty fast ca. 2s and it
buffers/caches "future" content, however to B it takes more than 6s and
it doesn't seem to buffer/cache. However A gets stuck periodically which
makes i
