RFC 2616 Compliance Check Fails Due To Content-Type Header Missing From Several Studio Pages Or From Some Of The Loaded Resources Like Javascripts, Css Or Images (Doc ID 2170803.1)

Last updated on AUGUST 10, 2016

Applies to:

Oracle Endeca Information Discovery Studio - Version 3.1.0 to 3.2.0 [Release 3.x]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------
The content-type header is missing on several Studio webpages.
Other Studio webpages are missing the entity-header content-type for some of the resources loaded in browser (javascripts, css, images etc).

EXPECTED BEHAVIOR
-----------------------
As per RFC 2616, any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body.

STEPS
-----------------------
The issue can be reproduced when performing a GET on /eid/html/js/barebone.jsp, with no reverse-proxies etc.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms