You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2008/12/27 14:55:44 UTC
[jira] Closed: (NUTCH-531) Pages with no ContentType cause a Null
Pointer exception
[ https://issues.apache.org/jira/browse/NUTCH-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki closed NUTCH-531.
-----------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 1.0.0
Assignee: Andrzej Bialecki
> Pages with no ContentType cause a Null Pointer exception
> --------------------------------------------------------
>
> Key: NUTCH-531
> URL: https://issues.apache.org/jira/browse/NUTCH-531
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 0.9.0, 1.0.0
> Reporter: Carl Cerecke
> Assignee: Andrzej Bialecki
> Fix For: 1.0.0
>
> Attachments: NUTCH-531-draft.patch
>
>
> Some pages cause a null pointer exception because the contentType is missing (e.g. http://www.absoluteit.co.nz and http://defence.allmedia.co.nz)
> The solution that I used was to change line 165 (trunk) of Content.java to:
> Text.writeString(out, contentType != null?contentType:"");
> rfc2616 states this should be application/octet-stream if we don't know the content type, and can't figure it out.
> But perhaps the problem is in getContentType() at line 281 (trunk). I don't yet know enough of how it is connected together to determine where the best place for fixing this bug is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.