Cisco Cisco Web Security Appliance S170 사용자 가이드

The requested file is not found on the server

 – The URL provided for the feed file points 

to an invalid resource. Ensure the correct file is available on the specified server.

Content validation errors

Failed to validate the content of the field

 – The content of the feed file is invalid.

Parsing errors

The Cisco Feed Format .csv file must contain one or more entries, where each entry is a site 
address or a valid regex string, followed by a comma and then the addresstype (which can be 
either 

site

 or 

regex

). If this convention is not followed for any entry in the feed file, a parsing 

error is thrown.

Also, do not include 

http://

 or 

https://

 as part of any 

site

 entry in the file, or an error will 

occur. In other words, 

www.example.com

 is parsed correctly, while 

http://www.example.com

 

produces an error.

The XML feed file obtained from a Microsoft server is parsed by a standard XML parser. Any 
inconsistencies in the XML tagging are also flagged as parsing errors.

The line number of a parsing error is included in the log. For example:

Line 8: 'www.anyurl.com' - Line is missing address or address-type field.

 Line 8 

in the feed file doesn’t include a valid address or regex pattern, or an addresstype.

Line 12: 'www.test.com' - Unknown address type.

 Line 12 has a invalid addresstype; the 

addresstype can be either 

site

 or 

regex

.

When providing a .csv file for the External Live Feed Category > Cisco Feed Format option while 

, you may encounter a “406 not acceptable” 

error when fetching the file if the Cisco Feed Format server is running Internet Information Services 
(IIS) version 7 or 8 software. Similarly, the 

feedsd

 log will report something like: 

31 May 2016 

16:47:22 (GMT +0200) Warning: Protocol Error: 'HTTP error while fetching file from 

the server'

.

This is because the default MIME type for .csv files on IIS is 

application/csv

 rather than 

text/csv

. 

You can remedy the problem by logging into the IIS server and editing the MIME type entry for .csv 
files to be 

text/csv

.

If you copy and paste the contents of a .csv (text) feed file from a UNIX or OS X system to a Windows 
system, an extra carriage return (

\r

) is added automatically and this can make the feed file malformed.

If you manually create the .csv file, or if you transfer the file from a UNIX or OS X system to a Windows 
server using SCP, FTP, or POST, there should be no problem.