[
https://issues.apache.org/jira/browse/OLINGO-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063725#comment-15063725
]
Gyula Árpád Tóth commented on OLINGO-839:
-----------------------------------------
Hi Christian,
I checked your commit and I have only one question. It seemed to be safe to
call getContentType with null and the http headers. The headers may contain an
Accept header, so we do not have to guess the response content type. Am I wrong
with this observation?
Thanks,
Gyula
> Invalid URL may return http status code 500 instead of 400
> ----------------------------------------------------------
>
> Key: OLINGO-839
> URL: https://issues.apache.org/jira/browse/OLINGO-839
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.5
> Reporter: Gyula Árpád Tóth
> Assignee: Christian Amend
> Priority: Minor
> Fix For: V2 2.0.6
>
> Attachments: 0001-OLINGO-839-Broken-URL-response.patch
>
>
> Broken urls like:
> http://services.odata.org/OData/OData.svc/Suppliers?$filter=Address/City%20eq%20%27Redmond%2
> should set the http status code to 400. In olingov2 the status code is set
> 500, because once the url parsing failed, in the ODataExceptionWrapper the
> url is parsed again and failed again, resulting in status code 500.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
