Releases: moia-oss/lambda-kotlin-request-router
Releases · moia-oss/lambda-kotlin-request-router
Ignore content-type header when route expects none
0.6.3 Ignore content-type header when route expects none.
Use Base64 encoding for Proto handling
Make response location optional (#11) * Make response location optional * Format kotlin
Return 403 instead of 401 when permissions are missing
0.6.1 Return 403 instead of 401 when required permissions are missing (#9)
More flexible error serialization
- go back to guava media type
- more flexible error serialization and enabling errors in proto format
Fix no-content response
0.5.2 Fix no-content response (#5)
Add null safety check for missing request path
Background: The serverless warmup lambda plugin invokes the lambda without any headers or a request path present. This should not throw exceptions.
Add permissions handling
Add permissions handling (#3) * Add permissions handling * Add documentation * Add hint about JWT verification * Use constant to avoid duplicating default values * Use equals with ignoreCase switch
Use Apache ContentType instead of Guava MimeType
Use Apache ContentType instead of Guava MimeType (#2) * Use Apache ContentType instead of Guava MimeType * Use Apache ContentType instead of Guava MimeType in ProtoSerializationHandler
Catch-all Path Variables Parameters / Greedy Path Parameters
Also see AWS documentation for greedy path variables:
https://aws.amazon.com/blogs/aws/api-gateway-update-new-features-simplify-api-development/
0.3.1
avoid logging function reference