Hi
What is the difference between the mp4 module and the slice module for
streaming mp4 videos in nginx? Both seem to work on streaming mp4 files but
I can't really see the difference.
On another aspect, the slice module seems to work nicely with the caching.
Where slices from cache module are st
In order to redirect http to https, you have to define a listener rule in
the ALB that redirects all traffic on port 80 to port 443 (of the ALB) with
the original path and query parameters. The status code should be a 301
(permanent redirection). That's the context between the client and the ALB.
This is still a big mystery to me. Upgrading to nginx 1.16.1 didn’t help.
As far as I can understand, the nginx master process IS running with root
privileges.
> On 19 Sep 2018, at 2.00, Palvelin Postmaster via nginx
> wrote:
>
> Why am I getting these log warn/emerg? Running Nginx 1.14.0 on
I have AWS ALB in front of an instance running nginx. I want to terminate https
at the load balancer.
I have setup ALB's http listener to redirect http to https and forward https to
the instance’s port 80.
I’m switching from using apache to nginx. My apache currently responds on a
single port
I have AWS ALB in front of an instance running nginx. I want to terminate https
at the load balancer.
I have setup ALB's http listener to redirect http to https and forward https to
the instance’s port 80.
I’m switching from using apache2 to nginx. My apache responds on a single port
80. In my
On 09/04, Jürgen Wagner (DVT) wrote:
> This is the effect you get by having the HTTP equivalent of a symbolic link
> in the NGINX (visible to the browser), not in the file system (which is
> opaque to users). The file system link will (over time) serve different
> contents under the same URL, so in
Hi Lewis,
no, that won't cause double requests.
/myapp/current/blah.html
307 => /myapp/releases/1.2.0/blah.html
and from thereon (as we did not redirect internally, but rather
externally), any further accesses will happen unter the true "releases"
path (ideally, as relative URLs).
That's
On 09/04, Jürgen Wagner (DVT) wrote:
> Now, you want to be able to say what is the "current" version and reflect
> this in the URL namespace as well. In the file system, that's a symbolic
> link. In the URL namespace of NGINX, that could be a redirection (status
> code 307). Both approaches would w
Hello.
On 04/09/2019 06:20, j94305 wrote:
> A little correction to my earlier message: IPv6 addresses also seem to work.
> In my test, I was checking for a dot in the key, and that excluded IPv6
> addresses.
>
> However, CIDR ranges still fail.
>
Please approach nginx-plus support with this issu
