Technical Alerts

SmartFilter database download is reporting "Bad Request" for the incremental download, but full control file download works properly

Technical Alerts ID:    TFA96
Version:    4.0
Status:    Published
Published date:    03/26/2012
Updated:    04/30/2012
 

Affected products and versions

All ProxySG platforms running the SmartFilter database, including all SGOS versions except for the following versions in which this issue has been fixed:

  • Fixed in SGOS 6.2.9.1 and higher

Please note that this issue does not affect the ProxySG's ability to perform content filtering and there is no interruption in service.

The only impact is that a full database needs to be downloaded on a daily basis instead of the incremental update, which means higher bandwidth usage at the time of the update.

 

Problem description

When looking at the download log, we can see that the ProxySG got a "Bad Request" warning when attempting to download the incremental update file, but following the error, the complete database (full control file) is downloaded successfully.
 
Download log:
  SmartFilter download at: 2012/03/21 13:36:43 -0400
  Downloading from: list.smartfilter.com
  Checking incremental update
    Installed database version: 32775
    Current published version:  32780
    Applying incremental updates
    Applying increment: 32776
      Warning: Bad Request
  Download failed

Previous download:
  SmartFilter download at: 2012/03/21 09:07:31 -0400
  Downloading from: list.smartfilter.com
  Checking incremental update
    Installed database version: 32769
    Current published version:  32775
    Applying incremental updates
    Applying increment: 32770
      Warning: Bad Request
  Downloading full control file
    Full download complete
  Database size:        396467068
  Building database
    Database version:   32775
    Database date:      Wed, 21 Mar 2012 11:45:37 UTC
    Database expires:   Wed, 25 Apr 2012 11:45:37 UTC

Status

This issue has been fixed in SGOS 6.2.9.1. 

Workaround

There currently is no workaround for this issue, but as mentioned above, there is also no impact in the ProxySG's content filtering capabilities. 

 

 



Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question