[
https://issues.apache.org/jira/browse/OLINGO-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309831#comment-16309831
]
M Carissimi commented on OLINGO-1220:
-------------------------------------
Hello Christian,
thank you for the clarification. We run the OData service on Glassfish and I
have been able to get the container to accept requests with the slash character
by setting the http listener's encoded-slash-enabled to true.
I have not found a suitable solution for the backslash character, do you have
any suggestion on how to get this working in Glassfish?
Regards
Michele
> Bad request (error 400) for entries with slash or backslash character in
> string literal of key predicate
> --------------------------------------------------------------------------------------------------------
>
> Key: OLINGO-1220
> URL: https://issues.apache.org/jira/browse/OLINGO-1220
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.9, V2 2.0.10
> Reporter: M Carissimi
> Assignee: Christian Amend
> Priority: Critical
>
> Hello,
> our OData service implemented with Olingo 2.0.x refuses to accept requests
> for entries where the string literal of a key predicate contains the slash
> (/) or backslash (\) characters. In both cases encoding the slash or
> backslash character with the corresponding code (%2F and %5C respectively)
> does not resolve the issue. In all cases an error 400 is returned by Olingo
> These are some example of failing URLs:
> https://<servername>/odata/WELL('Alice-09-d%2Fe')
> https://<servername>/odata/WELL('Alice-12-k%5Cm')
> Can you please investigate this issue and let me know if there's anything we
> can do in our code to prevent it from happening?
> Regards
> Michele
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
