[CONNECTORS-1571] Web Crawler Connector checks different MIME type than it is sending down the pipeline

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: ManifoldCF 2.10
• Component/s: Web connector
• Assignee: Markus Schuch
• Reporter: Markus Schuch
• Created: 14/Jan/19 14:24
• Updated: 23/Aug/19 20:15
• Resolved: 23/Aug/19 20:15

Description

The Web Crawler Connector extracts the MIME type from the request Content-Type header.
Then it truncates the possible charset=whatever_encoding and lets the pipeline check if the resulting MIME type (without the charset) activities.checkMimeTypeIndexable(contentType); should be ingested.

When sending the actual RepositoryDocument it sets the full MIME type (with the charset) in the document. This is no major bug, but a small inconsistency since the HttpPoster of the Solr Output Connector performs a "hard" check of the MIME type again which can have different outcome than the preceding check activity.

I think this was introduced or (better) revealed with CONNECTORS-1482.

Example:

• In my scenario a crawled webpage has Content-Type text/html; charset=utf-8
• the activities.checkMimeTypeIndexable(contentType); is called with text/html
• the hard check performed by the Solr Connector is called with text/html; charset=utf-8

Issue Links

• is related to: CONNECTORS-1482 Mime type exclusion and document length exclusion in Solr output connector don't apparently work
• relates to: CONNECTORS-1621 Fix for CONNECTORS-1482 broke Solr / Tika integration