Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource record always rendered as text/html #68

Closed
kngenie opened this issue Jan 31, 2015 · 1 comment
Closed

Resource record always rendered as text/html #68

kngenie opened this issue Jan 31, 2015 · 1 comment
Labels

Comments

@kngenie
Copy link
Member

kngenie commented Jan 31, 2015

Resource record is always rendered as text/html, regardless of Content-Type WARC header field.

This is due to a lack of metadata record support in JWATResource. It does not return Content-Type header field from its getHttpHeaders() method, thus Tomcat supplies default value text/html.

Known internally as WWM-126.

@kngenie kngenie added the bug label Jan 31, 2015
@kngenie
Copy link
Member Author

kngenie commented Jan 31, 2015

It turned out JWATResource does not a test suite, and it is not fully compliant to Resource interface contracts. Implemented tests, and updated JWATResource to pass all tests.

Fix is in eea650b .. c52d8b3 and 69a4f08. Merged to master c1dd221.
Merged to iipc/master in 1dbd4f3 (iipc#195).

@kngenie kngenie closed this as completed Jan 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant