You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Ramya (JIRA)" <ji...@apache.org> on 2019/06/04 04:42:00 UTC

[jira] [Commented] (OLINGO-1362) OData V2: Missed http status code 420

    [ https://issues.apache.org/jira/browse/OLINGO-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855304#comment-16855304 ] 

Ramya commented on OLINGO-1362:
-------------------------------

This is fixed as part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=8449e389b6166bd9a38473a599d8c7be91c31c20

> OData V2: Missed http status code 420
> -------------------------------------
>
>                 Key: OLINGO-1362
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1362
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 2.0.11
>            Reporter: Ramya
>            Priority: Major
>
> Http status code 420 is not listed in org/apache/olingo/odata2/api/commons/HttpStatusCodes.java
> 420 http status code is a deprecated response and also it used to be the return code for Twitter Search and Trends API when the client is being rate limited. This 420 status code is not added in the olingo HttpStatusCodes and hence the applications get 500 Internal server error.
>  (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)