Extensions doesn't install from a whitelisted thirdparty source |
|||
Issue descriptionExtensions are listed in the force installed extensions policy like this: ExtensionInstallForcelist: cjpalhdlnbpafiamejdnhcphjbkeiagm;https://srv01.chrome.local/updade.xml gcbommkclmclpchllfjekcdonpmejbdp;https://srv01.chrome.local/update.xml ExtensionInstallSources: https://srv01.chrome.local/* according to server logs chrome issues a request to the update url 2017-11-07 09:36:33 172.18.80.7 GET /update.xml os=win&arch=x64&nacl_arch=x86-64&prod=chromecrx&prodchannel=&prodversion=62.0.3202.89&lang=ru&acceptformat=crx2,crx3&x=id%3Dcjpalhdlnbpafiamejdnhcphjbkeiagm%26v%3D0.0.0.0%26installsource%3Dnotfromwebstore%26uc&x=id%3Dgcbommkclmclpchllfjekcdonpmejbdp%26v%3D0.0.0.0%26installsource%3Dnotfromwebstore%26uc 443 - 172.18.80.5 Mozilla/5.0+(Windows+NT+6.1;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/62.0.3202.89+Safari/537.36 - 500 0 64 15 the file seems properly formated and loads if the above url is pasted in the browser. File contents: <?xml version='1.0' encoding='UTF-8'?> <gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'> <app appid='cjpalhdlnbpafiamejdnhcphjbkeiagm'> <updatecheck codebase='https://srv01.chrome.local/1.14.16_0.crx' version='1.14.16' /> </app> <app appid='gcbommkclmclpchllfjekcdonpmejbdp'> <updatecheck codebase='https://srv01.chrome.local/2017.10.30_0.crx' version='2017.10.30' /> </app> </gupdate> Any ideas what could be the reason or how to diagnose this further.
,
Nov 7 2017
The log you included looks like an IIS server log, and it appears to be returning an HTTP 500 indicating a server issue. When you tested it in your browser, did you include the full query string? Does the policy really say 'updade.xml' or was that just a typo when creating the bug? Normally the list of extensions has a comma between them when viewed in chrome://policy (cjpalhdlnbpafiamejdnhcphjbkeiagm;https://srv01.chrome.local/updade.xml,gcbommkclmclpchllfjekcdonpmejbdp;https://srv01.chrome.local/update.xml). Did chrome://policy show these as parsing okay? I've only been using the http protocol for update URLs rather than https since extensions do their own validation. Could it be there isn't a trusted TLS cert for the .local address causing a problem?
,
Nov 8 2017
trusted TLS cert enable, and ok chrome://policy show ok
,
Nov 8 2017
the same problem, when i change to http
,
Nov 8 2017
Can you try changing your code on IIS to respond with an HTTP 200 rather than an HTTP 500? IIUC the code below would seem to indicate that only an HTTP 200 response to the manifest request (or loading from file://) is considered a valid response. https://cs.chromium.org/chromium/src/extensions/browser/updater/extension_downloader.cc?rcl=9420a458c5bdecef31b8793ccdc09325a846c55a&l=576
,
Nov 9 2017
2017-11-09 03:01:48 172.18.80.7 GET / os=win&arch=x86&nacl_arch=x86-64&prod=chromecrx&prodchannel=stable&prodversion=39.0.2171.95&lang=en-US&x=id%3Dcjpalhdlnbpafiamejdnhcphjbkeiagm%26v%3D0.0.0.0%26uc&x=id%3Dgcbommkclmclpchllfjekcdonpmejbdp%26v%3D0.0.0.0%26uc 80 - 172.18.80.7 Mozilla/5.0+(Windows+NT+6.3;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/39.0.2171.95+Safari/537.36 - 200 0 0 171
,
Nov 9 2017
,
Nov 10 2017
nrpeter@, assigning this to you for now to get it out of triage. Feel free to re-assign if appropriate. :)
,
Nov 10 2017
Navynie.v does your response in comment #6 mean that you've fixed IIS to return HTTP 200 responses but the issue still persists? If this is a Windows machine is it joined to a domain (Active Directory)?
,
Nov 13 2017
Yes, issue still persists. And windows machine is joined to a domain (Active Directory). |
|||
►
Sign in to add a comment |
|||
Comment 1 by rdevlin....@chromium.org
, Nov 7 2017