nginx

Doing DevOps You’ve probably heard the parable of the people who encounter an elephant in a pitch-dark room. Each touches a different part of the animal – and describes it completely differently. The leg is a pillar; the trunk is a tree branch; the tail is a rope. Everyone’s right about the specifics – but it takes the whole group to understand what they’re “seeing”. This parable is a useful and common metaphor for how DevOps effectively brings together divergent viewpoints to improve the speed, predictability, and efficiency of app development and deployment. Before the DevOps movement took hold, groups within IT – Operations, Development, QA – were siloed, functioning within their own universes. Each group had its own way of looking at the development and deployment cycle. Each group’s ideas about the nature of the beast were based on that group’s goals, role [ more… ]

Announcing a Change to the Certificate for the NGINX Plus Repository In our ongoing efforts to improve the security of our products, we’ve made a change that affects the way NGINX Plus is installed and updated. We are replacing the self-signed certificate we previously used to secure the NGINX Plus repository with a certificate from GlobalSign, a well-known and trusted Certificate Authority (CA). With a CA-signed certificate, clients can now verify the certificate we present and be assured that the code they are downloading is from NGINX. The next time you install or update NGINX Plus, you might see an error such as: On Amazon Linux, CentOS, Oracle Linux, and RHEL: curl#60 – “Peer’s certificate issuer has been marked as not trusted by the user.” On Debian and Ubuntu: server certificate verification failed. CAfile: /etc/ssl/nginx/CA.crt CRLfile: none If you get [ more… ]

Supporting HTTP/2 for Google Chrome Users table, th, td { border: 1px solid black; } th { background-color: #d3d3d3; align: left; padding-left: 5px; padding-bottom: 2px; padding-top: 2px; line-height: 120%; } td { padding-left: 5px; padding-bottom: 5px; padding-top: 5px; line-height: 120%; } Users of the Google Chrome web browser are seeing some sites that they previously accessed over HTTP/2 falling back to HTTP/1. This is because of a policy change in the most recent update to Chrome, released in late May, which removes support for NPN, one method for upgrading a connection to HTTP/2. The only way Chrome users can continue using HTTP/2 to access these websites is by switching to a different browser. Website administrators can restore HTTP/2 support for Chrome users by upgrading their OpenSSL installation to the recently released 1.0.2 version. Unfortunately, this requires either a major operating system [ more… ]