Bug 1327539 - Wrong Content-Type in error response from odata
Summary: Wrong Content-Type in error response from odata
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ER3
: 6.3.0
Assignee: Van Halbert
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 10:35 UTC by Andrej Smigala
Modified: 2016-08-24 11:42 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:42:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4143 0 Blocker Closed Wrong Content-Type in error response from odata 2016-10-31 15:49:01 UTC

Description Andrej Smigala 2016-04-15 10:35:17 UTC 
When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail.


Steps to Reproduce:
1.start DV, add user with odata role
2. $ curl -D - -u user:user 'http://localhost:8080/odata4/ModeShape/ModeShape?filter=intkey%20eq%20@p1&@p1=1&@p1=1'
Comment 2 JBoss JIRA Server 2016-04-18 22:38:50 UTC 
Anu Saji <asaji> updated the status of jira TEIID-4143 to Coding In Progress
Comment 3 JBoss JIRA Server 2016-04-18 22:38:55 UTC 
Anu Saji <asaji> updated the status of jira TEIID-4143 to Open
Comment 4 JBoss JIRA Server 2016-04-21 21:24:22 UTC 
Ramesh Reddy <rareddy> updated the status of jira TEIID-4143 to Coding In Progress
Comment 5 JBoss JIRA Server 2016-04-22 22:31:49 UTC 
Ramesh Reddy <rareddy> updated the status of jira TEIID-4143 to Resolved
Note You need to log in before you can comment on or make changes to this bug.