vArmour's RESTful API response should handle more error code besides HTTP 200 OK

[Gary Duan]

When handling rest API responses, vArmour's rest API interface only handle HTTP 200 OK. It cannot distinguish 400, 401 and 404 etc.

Properly handle these response code will improve the robustness and performance of the driver.

[Gary Duan (gduan)]

This bug request is also based on Salvatore's code review on vArmour's FWaaS driver implementation. We didn't have time to address it at the time.

[Eugene Nikanorov (enikanorov)]

Is this still a relevant bug?

[Gary Duan (gduan)]

Hi, Eugene,

It is not really relevant now. We have refactored our plugin and driver and
have been planning to upstream it.

Thanks,
Gary

On Sun, Nov 23, 2014 at 10:19 PM, Eugene Nikanorov <email address hidden>
wrote:

> Is this still a relevant bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1222973
>
> Title:
> vArmour's RESTful API response should handle more error code besides
> HTTP 200 OK
>
> Status in OpenStack Neutron (virtual network service):
> In Progress
>
> Bug description:
> When handling rest API responses, vArmour's rest API interface only
> handle HTTP 200 OK. It cannot distinguish 400, 401 and 404 etc.
>
> Properly handle these response code will improve the robustness and
> performance of the driver.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1222973/+subscriptions
>

[Eugene Nikanorov (enikanorov)]

Closing per previous comment