Website connector release notes
Website Connector 2.0.1.1
This release of the Website connector features the following enhancements. For more information about the connector, see About the Website connector.
System Enhancements
| Feature | Description |
|---|---|
| Filtering enhancements |
Admins can now filter out file types, other websites, and URL paths directly in the connector UI. For more information, see How to set up and configure the Website connector. |
| Crawling enhancements |
Admins can now specify multiple website URLs in the Website connector general settings configuration. To allow for this, the following must be valid:
For more information, see How to set up and configure the Website connector. |
| Supported mime types | The Web.config file now includes the list of default mime types that are configured for the Website connector. Admins can add new The file types in this list of mappings can be used in the Settings field for the Website Connector configuration. For more information, see How to set up and configure the Website connector. |
| Support for excluding links | Admins can now specify the links that they don't want to be included in crawls by specifying them in the excluded tags custom settings for their Website connector. For more information, see How to set up and configure the Website connector. |
| Support for NTLM authentication | The Website connector now supports crawling websites configured with NTLM authentication. |
Fixed issues
-
During a crawl with the Website connector, broken links were being passed to Connectivity Hub. The connector now ignores broken links identified in crawls. (BAI-9270)
-
If a page was deleted after a full crawl was performed, the page would still be returned when a subsequent incremental crawl Scanning and capturing only new data from all of your content sources. This data did not exist when the last crawl was run. was run. (BAI-9390)
-
When a file was saved to the disk from Test Bench, the file did not have an extension. (BAI-9796)