You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Eugenio Lentini (JIRA)" <ji...@apache.org> on 2014/05/28 10:45:02 UTC

[jira] [Comment Edited] (OLINGO-305) case-sensitive vs case-insensitive

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

Eugenio Lentini edited comment on OLINGO-305 at 5/28/14 8:44 AM:
-----------------------------------------------------------------

Hi Stephan,
I have not tested yet in another container but it could be. According to the spec the field name has to be case-insensitive.

Thanks.
Eugenio


was (Author: black@t):
Hi Stephan,
I have not tested yet in another container but it could be. According to the spec the field name has to be case-insensitive.

Do you know when the fix will be available?

Thanks.
Eugenio

> case-sensitive vs case-insensitive
> ----------------------------------
>
>                 Key: OLINGO-305
>                 URL: https://issues.apache.org/jira/browse/OLINGO-305
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>            Reporter: Eugenio Lentini
>            Assignee: Stephan Klevenz
>             Fix For: V2 1.3.0
>
>
> Basically before updating to release 1.2.0 this code was working correctly
> String auth = ctx.getRequestHeader("Authorization");
> after I have to use
> String auth = ctx.getRequestHeader("authorization");
> because probably the method has been change to case-sensitive, I guess this could led to some issues to other people.
> Thanks a lot for the attention.
> Eugenio



--
This message was sent by Atlassian JIRA
(v6.2#6252)