2 Replies Latest reply on Nov 17, 2015 12:42 PM by malware-alerts

    Chrome 46.0.2490.86 doesn't respond to HTTP407 (NTLM) when doing FTP over HTTP ?

    malware-alerts
      • Using MWG 7.5.2.2 in explicit proxy mode.
      • MWG is configured to send 'anonymous' FTP logon when using FTP over HTTP.

       

      Users trying to download files from an FTP site using Chrome (FTP over HTTP) receive the "You must be authenticated" block page.

       

      When lookng at a packet trace when reproducing the issue, we can see that Google Chrome is NOT answering the HTTP 407 response from the proxy AND it is NOT sending a "User-Agent' header with it's request :

       

      FTP_Chrome_NTLM_User-Agent.png

      (In the picture above, Yellow is the client and Black is the MWG)

      • The request headers are in the red highlight : no trace of 'User-Agent'.
      • 2 ACK packets (not shown) are sent by the client after the HTTP407, nothing else.

       

       

      When doing the same operation with IE11, everythng works normally:

       

      FTP_IE_NTLM_User-Agent.png

      (In the picture above, Yellow is the client and Black is the MWG)

      • The request headers in the red highlight show the 'User-Agent' header being sent by the browser.
      • NTLM negotiation completes normally between the browser and the MWG. User is authenticated and allowed to proceed to the FTP site and download the requested file.



      1. I don't recall having FTP over HTTP issues with prior versions of Chrome when using FTP over HTTP with anonymous credentials ((unfortunately can't validate).
      2. Google Chrome properly deals with the HTTP 407 response when browsing HTTP.
      3. Google Chrome sends the User-Agent header in it's request when browsing HTTP/HTTPS

       

      Anybody else noticed that?