Inconsistency of HttpRequest interface factory methods

[vonZeppelin]

Task List

• Steps to reproduce provided
• Stacktrace (if present) provided
• Example that reproduces the problem uploaded to Github
• Full description of the issue provided (see below)

Steps to Reproduce

1. Create POST or PUT or PATCH HttpRequest instance via corresp. static method with null as body.

Expected Behaviour

It is possible to create a POST / PUT / PATCH HttpRequest instance with null body via interface factory methods. Use-case for this is to make sending of the POST / PUT / PATCH request with empty body via, for example, RxHttpClient possible. A workaround is to use empty string as body or build the request with HttpRequest.create() (?).

Actual Behaviour

NullPointerException Argument [body] cannot be null will be thrown. DELETE instance can be created with null body though.

Notes

HttpRequest.getBody() returns Optional, so enforcing non-null bodies looks excessive.

Example Application

Not required, issue is obvious from the source code.

[vonZeppelin]

This is fixed in Micronaut 2.5.6