ReadyAPI requires optional location header when receiving a temporary redirect (307)

While testing a new RESTful service we found that ReadyAPI requires a location header for redirection when receiving a response with HTTP status 307. If there is no redirection-URL ReadyAPI throws a NullPointerException.

It seems that the standard says a location header should not must be generated:

The server SHOULD generate a Location header field in the response containing a URI reference for the different URI. The user agent MAY use the Location field value for automatic redirection. The server's response payload usually contains a short hypertext note with a hyperlink to the different URI(s).

Changing the sourcecode to cater for ReadyAPI's "needs" proved to not be a good idea as it caused problems in the application calling the RESTful service.

cURL, Postman and Spring's RestTemplate can deal with a temporary redirect without the location header. Is there a way to make ReadyAPI the same way via configuration or is this a bug?