Skip to content

v1.11.0
Compare
Choose a tag to compare
@XVincentX XVincentX released this 17 Aug 14:20
· 316 commits to master since this release
v1.11.0
74f2f25

Express Gateway v1.11.0 has been released.

This release fixes some bugs reported by users that are continuously using Express more and more and brings the addition of a really important feature for proxy policy so that Express Gateway finally catches up with some missing path management features that were missing.

Added

  • The Proxy Policy for Express Gateway now supports a new parameter called stripPath that defaults to false. This is particularly useful when you want to completely own both the URL space of your backend server as well the one exposed by Express Gateway. Given the new feature, we decided to revamp a little bit our Proxy Policy Docs with a section dedicated to the Path Management showing when you should use a flag and when not. #777
  • Although this is not intrinsically Express Gateway related, we have now an Official Helm Chart, that means you can install Express Gateway on your Rancher or Kubernetes Cluster with a single command. We'll update the website as soon as possible with this new great addition. helm/charts#7130

Fixed

  • The base condition schema is now correctly returned by the /schemas Admin API Endpoint #797
  • The keyauth schema name is now correctly named key-auth, for consistency #781
  • We kindly received some contributions on our docs and our Readme from @alamgirqazi — Thanks! 🎉 #773
  • While using Express Gateway in production we found out that invalid configuration could be sent to the gateway through the Admin API. Although the gateway was correctly validating the gateway.config content, it wasn't validating all the policies inside it — that is a room for an inconsistent configuration that could ultimately lead to a crash and inability to start EG in case you'd restart your instance/container. This is now fixed. Thanks to @kolbinski for finding out this little monster #782 #799
  • Fixed a missing field in oauth2-introspect JSON Schema #779

Changed

  • We have removed the old, unused migration framework as we do not plan to do any other data model adjustment in the Gateway until we go for 2.0 release #775
  • As always, we've bumped up all our dependencies and change some parts of code that are now deprecated in Node 10. We still support Node 6 but we'll progressively remove all these parts. #787
  • For security reasons, we've decided to disable the X-Powered-By header returned implicitly by Express JS. In case you need it back, you can restore it through a custom plugin. #769
  • We have collected some other feedback on our official Docker Image by the Docker Official Program — now EG is not wrapped in a bash command before being ran #770

Express Gateway in production? Let us know!

As always, we're open to any feedback and ready to hear your story of putting Express Gateway in production. In case you're interested, please reach us on Gitter, via email or in any way you want. We can send you swags!

Assets 2
Loading