Why the Status Page is not displayed in Chrome browser when using FTP over HTTP?


This article applies to:

  • All SWG versions

Question:

  • Why the Status Page is not displayed in Chrome browser when using FTP over HTTP protocol? (when setting port 8080 in the proxy settings for FTP transactions on the browser side)

Reply:

The header in the GET request coming from the browser which is mandatory for activating the Status Page is the User-Agent header.

This is visible in the "Administration >  System Settings >  Scanning >  Scanning Options" section of the SWG GUI (part of the configuration) - see the screenshot below:



Chrome browser doesn't include User-Agent header in the GET request when FTP over HTTP protocol is being used.
Please see below the comparison of the GET requests that are sent by the browsers for retrieving the same file when using Chrome and Firefox:

1) Chrome browser - no User-Agent header is included in the GET request:



2) Firefox browser - User-Agent header is included in the GET request:


Notes:

This article is applicable only when FTP over HTTP protocol is used (port 8080 for FTP transactions is set on the browser side in the proxy settings). For other protocols (e.g. HTTP etc.), the behavior is different.

Last Modified 9/16/2015.
https://support.trustwave.com/kb/KnowledgebaseArticle20384.aspx