[jira] [Resolved] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz resolved OLINGO-1097.
--
Resolution: Fixed
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz closed OLINGO-1097.
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941631#comment-15941631
]
Michael Bolz commented on OLINGO-1097:
--
Hi [~dtretyakov],
Thanks for the contribution.
I fixed a minor checkstyle issue and pushed it with [this
commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=cceffb31024be8e94a210c344ee68b6b98ddfdfb].
Best Regards, Michael
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (OLINGO-1097) Failure while parsing HTTP header fields joined by multiple whitespaces
[
https://issues.apache.org/jira/browse/OLINGO-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz reassigned OLINGO-1097:
Assignee: Michael Bolz (was: Christian Amend)
> Failure while parsing HTTP header fields joined by multiple whitespaces
> ---
>
> Key: OLINGO-1097
> URL: https://issues.apache.org/jira/browse/OLINGO-1097
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: Dmitry Tretyakov
>Assignee: Michael Bolz
> Labels: patch
> Fix For: V2 2.0.9
>
> Attachments:
> 0002-OLINGO-1097-Failure-while-parsing-HTTP-header-fields.patch
>
>
> `RestUtil` while parsing HTTP header values allow to join multiple field
> values with comma and only one white space it causes that after parsing
> values are prefixed by white spaces which causes exceptions in `ContentType`
> instantiation and as result leads to BadRequestException.
> See RFC 2616 4.2:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Example of failing HTTP accept header field value:
> {code}
> application/atom+xml, application/xml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz resolved OLINGO-1095. -- Resolution: Fixed > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OLINGO-1095) JPAQueryBuilder.normalizeMembers encounters issue when EmbedId
[ https://issues.apache.org/jira/browse/OLINGO-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941629#comment-15941629 ] Michael Bolz commented on OLINGO-1095: -- Hi [~evildracula], I added the additional check (see commit [OLINGO-1095 Check for embedded attributes|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=2d07b9fa98eb970a9554ca13a6492a568d79a1b0]). Please give feedback if it solves your issue. Kind Regards, Michael > JPAQueryBuilder.normalizeMembers encounters issue when EmbedId > -- > > Key: OLINGO-1095 > URL: https://issues.apache.org/jira/browse/OLINGO-1095 > Project: Olingo > Issue Type: Bug > Components: odata2-core >Affects Versions: V2 2.0.8 >Reporter: evildracula >Assignee: Michael Bolz > > org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder > normalizeMembers failed to process EmbedKeyId when JPA query is: > SELECT E1 FROM EndUser E1 WHERE E1.id.pid= 'T001' AND E1.id.rid= 'E001' > the normalized query will be: > SELECT DISTINCT E1 FROM EndUser E1 JOIN E1.id R1 WHERE R1.pid = 'T001' AND > R1.rid = 'E001' > |This will cause problem when validated by boolean > org.eclipse.persistence.jpa.jpql.AbstractSemanticValidator.validateCollectionValuedPathExpression(Expression > expression, boolean collectionTypeOnly)| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OLINGO-861) MetaDataParser unable to build EdmProvider from Edmx files with references
[ https://issues.apache.org/jira/browse/OLINGO-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941593#comment-15941593 ] rafiqkattangere commented on OLINGO-861: I think the recursive logic to load the schemas needs to be re-looked. Can you consider that? > MetaDataParser unable to build EdmProvider from Edmx files with references > -- > > Key: OLINGO-861 > URL: https://issues.apache.org/jira/browse/OLINGO-861 > Project: Olingo > Issue Type: Bug > Components: odata4-server >Affects Versions: (Java) V4 4.1.0 >Reporter: VIJAYASIMHA R NAGA >Assignee: Ramesh Reddy > Fix For: (Java) V4 4.2.0 > > Attachments: MyODataDemoService.zip, nestedreference.zip, > ServiceRoot.xml > > > Unable to build an EdmProvider from Edmx files with references to external > name spaces, (Method "readReference" in MetaDataParser.java from > server-core-ext library has a TODO remark to deal with this) > Ex: Having the below reference included in an Edmx file Uri="http://docs.oasis-open.org/odata/odata/v4.0/cs01/vocabularies/Org.OData.Core.V1.xml;> > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
