A microservices API Gateway built on top of Express.js
APACHE-2.0 License
Bot releases are hidden (Show)
Express Gateway v1.16.9 has been released.
This release fixes a missing option on the http proxy which was responsible for some poor performances
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.
Express Gateway v1.16.8 has been released.
This release fixes an OAuth2 introspection bug
oauth2-introspection
policy in multiple pipelines #942As 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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.7 has been released.
This release fixes some bugs reported by users and adds back the CI for Windows
system.config.yml
schema file has been update to make sure the namespace
Redis parameter is now mandatory, but with a sensible default. Without this value Express Gateway would be crashing.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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.6 has been released.
This release fixes some bugs reported by users and adds back the CI for Windows
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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.4 has been released.
This release fixes some bugs reported by users
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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.3 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more
plugins
admin endpoint #900As 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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.1 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more
base
schema as internal
and fix the Json Schema example property #891As 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.
Published by XVincentX over 5 years ago
Express Gateway v1.16.0 has been released.
This release brings some as bug fixes and an important rewrite of our condition engine that helped us close some important issues as well as implementing a very requested condition: JSON Schema validation!
json-schema
, has been added. This will let the gateway validate the payload of your request against a JSON Schema and then decide what to do according to the result. #882host
and hostname
used here and there. You'll now get a warning were appropriate as an invite to upgrade your configuration file. #876As 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.
Published by XVincentX over 5 years ago
Express Gateway v1.15.0 has been released.
This release bring as bug fix in our identity server and one of the most requested feature: the request/response transformer policy!
We have a brand new pair of policy that have been required by the community for really long time: Request and Response Transformers! These policies will let you hook into the request and the response headers and body before they're being processed to the downstream server or sent back to the client. This policy effectively deprecates the Headers
.
This has required a lot of effort on our side in terms of research, coming up with the DLS and making sure it works correctly in all the cases. We hope that this will help you going to the next level with Express Gateway #842 #869 #864
The CLI is now able to follow the pagination of the resources so that you can see all the users/applications or whatever you need in case you have a lot of data #762
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.
Published by XVincentX almost 6 years ago
Express Gateway v1.14.0 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more and some a new requested feature.
http
and https
servers. This might be particularly useful when using Express Gateway in Docker environments #846As 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.
Published by XVincentX about 6 years ago
Express Gateway v1.13.0 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more and some a small new requested feature.
Also β we have dropped support for Node 6. In case this platform is important for you, you might want to stick with any previous version.
Dockerfile
to better leverage the caching #819As 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.
Published by XVincentX about 6 years ago
Express Gateway v1.12.1 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more
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.
Published by XVincentX about 6 years ago
Express Gateway v1.12.0 has been released.
In this release we've been polishing some aspects of the JSON Schema to offer a better experience to Express Gateway developers, in particular in case you're building an UI for the project (and we are π )
The serviceEndpoint
parameter in the proxy policy is not mandatory anymore. In case it's not provided, the Gateway will respond with 502
#806
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!
In case you need help to deploy Express Gateway, custom development or even a managed Express Gateway deployment, LunchBadger offers professional services around the product. Poke us for further informations!
Published by XVincentX about 6 years ago
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.
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. #777base
condition schema is now correctly returned by the /schemas
Admin API Endpoint #797keyauth
schema name is now correctly named key-auth
, for consistency #781gateway.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 #799oauth2-introspect
JSON Schema #779X-Powered-By
header returned implicitly by Express JS. In case you need it back, you can restore it through a custom plugin. #769As 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!
Published by XVincentX over 6 years ago
Express Gateway v1.10.2 has been released.
This release brings a small fix on our logging story that has changed significantly because of the migration from Winston@2 to Winston@3.
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 π
Published by XVincentX over 6 years ago
Express Gateway v1.10.1 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 new policy and a small byproduct to our plugin framework that can potentially unleash new possibilities.
We have added a new policy called oAuth2 introspection
. This is particularly useful in case you're integrating Express Gateway with an external oAuth2 provider. Point your browser to our docs to know more. #747
We have added a new property to the egContext
object that plugins can leverage: requestStream
. This can be useful in case you want to inject a custom body instead of proxying the original one to a serviceEndpoint
. We're planning to write a blog post containing some interesting use cases very soon. #763
When using Json Web Tokens for the oAuth2 policy, you'll now receive a refresh_token
that you can use to grab a new access token. #758
The general Plugin Schema wasn't being evaluated, but simply registered in the system. Thanks to @ouvtk for spotting this and fixing it in #757
We have updated all our dependencies to latest versions, fixing some security alerts reported by the new npm audit
command. We're now running on Winston@3 as well. #738, #764
We have reorganized our eslint plugins so that we're installing only the one we're using for real as well as configure them properly. #732
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.
Published by XVincentX over 6 years ago
Express Gateway v1.9.1 has been released.
This release fixes some bugs reported by some users as well as some internal feedback received during our own usages.
puppetter
as a devDependency
. This was causing people to download 70M of Chromium even when using Express Gateway in production #726gateway.config
for API Endpoints. This was preventing some advanced scenarios reported by some of our users. #726bcrypt
native dependency to solely rely on the javascript version. This will remove the pain of compiling and dealing with native code. As this library is used in a non performance critical part, we see benefit in using the pure javascript version. We can revisit, if people will come up with the issue #730As 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.
Published by XVincentX over 6 years ago
Express Gateway v1.9.0 has been released.
This release brings some new features and bug fixes but more importantly we've payed down some chunks of our technical debt.
GET /credentials
, has been added to return all credentials registered in the system in bulk. #704 #710Promise
that will resolve with admin express app as well express apps for http
and https
serversΒ #700. Thanks @jinasonlin for the contribution! β€οΈ/apps
endpoint return a 500
status code, instead of a 409
#706/
and not, in the admin section #707As 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.
Published by XVincentX over 6 years ago
Express Gateway v1.8.2 has been released.
This release brings a small compatible change in the Admin API that was preventing one of our user to reach the production stage. In the spirit of the π , we decided to make it work right now.
id
field that you can use around for further queries and processing. #690As 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.
Published by XVincentX over 6 years ago
Express Gateway v1.8.1 has been released.
This release brings a small compatible change that was preventing one of our user to reach the production stage. In the spirit of the π , we decided to make it work right now.
expires_in
field, containing the expiration time of the current issued token. Note that this is not a bug, as the spec specified that this field is recommended
, but not mandatory. However, we've now added it for clarity so you do now have to rely on an hypothetic default value. #683As 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.