Bugs fixed

Changing and saving deployed proxies sometimes resulted in errors in the Edge management UI. This issue has been resolved.

5xx errors on responses

5xx HTTP errors occurred in situations where responses were complete according to the HTTP specification (no Content-Length or chunked encoding in target endpoint responses). Edge now treats those responses as complete.

NPEs

A NullPointerException was being thrown in the following situations:

In cURL requests when application/octet-stream content was passed without datatype --data-binary

When an API proxy bundle was missing the /apiproxy folder

The following message is now thrown instead: "Bundle is invalid. Unable to read/find APIProxy contents."

Trace: IP address

Beta trace feature: In API proxy trace sessions, if a target server is defined with an IP address, the transaction details now display the target server IP address rather than labeling it as "undefined".