I've been thinking of moving Apiman to the SemVer 2.x versioning
scheme (http://semver.org/) to provide a more meaningful and
consistent release number scheme.
Does anyone foresee that being a problem or have any thoughts?
I'm delighted to announce Apiman 1.3.1.Final is out, with a few notable new
features and improvements .
## 3scale-related functionality
You can now use the Apiman Gateway with the 3scale Manager/UI as an
alternative to the Apiman Manager/UI!
Using an overlay file you can augment your 3scale APIs with apiman
policies. There will hopefully be an opportunity for a more cohesive and
deeper integration with 3scale in the near future. Your feedback and demand
will drive this; I hope as many people try it out this functionality as
The new 3scale registry and plugin can perform all of the usual 3scale
functions, such as auth, reporting, metrics, and rate-limiting; with the
addition breadth of apiman's policies and pluggable functionality. The one
exception is that 3scale OAuth is currently not implemented (apiman's OAuth
plugins work as normal).
I'll be providing some blogposts over the coming days to demonstrate the
new features in a more digestible form, but the documentation is available
already. Just download the Vert.x distro and follow the instructions:
Expect some tooling soon to make generating JSON configurations for
headless and 3scale registries easier!
## Bug-fixes & Improvements
A good number of bugs were squashed in this release. Please try it out and
let us know if your issues persist (if you had any!).
The HTTP codes returned in error cases have been improved, including
connection issues (e.g. DNS, timeouts, etc). You should no longer get HTTP
500 for these, and the error messages should be more meaningful. Let us
know if there still seem to be issues in this area.
There were a few issues with TLS on the Vert.x gateway that have been
improved (e.g. devmode was not working properly). In the near future we'll
look to provide some sort of self-signed certificate generation so that TLS
can be configured OOTB. As an added bonus, if you provide ALPN Boot, then
HTTP/2 should just work.
## You can help!
Please try the new functionality and let us know how you find it. Your
demand and feedback is extremely important to the future direction of this
Expect another release very soon with more functionality, configurability
Some users have reported issues with the new GitBook documentation, so I'll
be looking to improve this.
 The more eagle-eyed amongst you will no doubt have noticed that most of
this was actually released a few days ago.
 You will need 3scale SaaS or on-prem for this to work.
 More in a blog soon.
Up until now there has been an issue with certain exceptions being
indistinguishable by HTTP code.
For example: timeouts and connection issues; API not found, API not
public; invalid accesses, etc, all return 500.
A community member requested us to remedy that, and I'm proposing to
do the following in this release:
Not found-related (like API not found): 404
Invalid access (like trying to access an API directly that isn't public): 401
Unable to connect to backend API: 502
Connector timeouts: 504
Is this likely to be an issue to anyone such that I should delay its
inclusion? Any other thoughts?