When compiling nginx with the
--with-libatomic=/usr/local/src/libatomic_ops-7.6.4 option, it is reported
that libatomic_ops.a does not exist.
If the libatomic_ops version is greater than 7.4.0, the libatomic_ops.a
file is located in ./src/.libs instead of ./src
see: https://github.com/ivmai/libat
Igor Sysoev Wrote:
---
> > On 18 Apr 2018, at 01:35, c0nw0nk
> wrote:
> >
> > Thank you for the help :)
> >
> > A new dilemma has occurred from this.
> >
> > I add a location like so.
> >
> > location ^~/media/files/ {
> > add_header X-Locati
Hello,
We have created a Nginx configuration which with multiple cnames and the
same domain name, and it is working correctly but we want to be able to
wildcard the domain name so during our system configuration we do not
have to modify the nginx configuration for different domains we are
ho
On 17.04.2018 21:30, djcza...@gmail.com wrote:
Is there a roadmap for nginScript
There is. The short term preliminary plan is:
- stream integration refactoring to match the way it done in
http
- access to shared memory storage
- base64 encode
__
> 3.Why does the protocol come up (even with the openssl command) as
> TLS_AES_256_GCM_SHA384 and not the TLS13 variants? ChaCha20-Poly1305 works
> in TLS1.2 just fine.
You can look at https://github.com/openssl/openssl/pull/5392
The default TLSv1.3 ciphersuites (and the way those are conf
> On 18 Apr 2018, at 01:35, c0nw0nk wrote:
>
> Thank you for the help :)
>
> A new dilemma has occurred from this.
>
> I add a location like so.
>
> location ^~/media/files/ {
> add_header X-Location-Order First;
> }
> location ~ \.mp4$ {
> add_header X-Location-MP4 Served-from-MP4-location;
>