[jira] Resolved: (NUTCH-24) Cannot handle incorrectly cased Content-Type

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/NUTCH-24?page=all ]
     
Chris A. Mattmann resolved NUTCH-24:
------------------------------------

    Fix Version: 0.8-dev
     Resolution: Fixed

This issue was addressed by NUTCH-139, the fault tolerant Metadata container. 

> Cannot handle incorrectly cased Content-Type
> --------------------------------------------
>
>          Key: NUTCH-24
>          URL: http://issues.apache.org/jira/browse/NUTCH-24
>      Project: Nutch
>         Type: Bug
>   Components: fetcher
>     Reporter: Stefan Groschupf
>     Priority: Minor
>      Fix For: 0.8-dev

>
> transfered from:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1014459&group_id=59548&atid=491356
> submitted by:
> boconnor
> Not really a bug but in many cases web servers give the 
> incorrect header of "Content-type" instead of "Content-
> Type" - notice the lowercase "t".
> This is particullary true of IIS. This results in the inability 
> to resolve the content type (or in fact resolving it to 
> nothing) resulting in the document not getting indexed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira