chromium-browser proxy - fix

[mama21mama]

chromium-browser --proxy-server=192.168.0.2:31028

Error 111 (net::ERR_TUNNEL_CONNECTION_FAILED): Error desconocido.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: chromium-browser 17.0.919.0~svn20111026r107304-0ubuntu1~ucd1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CrashDB: ubuntu
Date: Thu Oct 27 12:34:30 2011
Desktop-Session:
 DESKTOP_SESSION = None
 XDG_CONFIG_DIRS = None
 XDG_DATA_DIRS = None
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
ThirdParty: True
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (12 days ago)
chromium-default: CHROMIUM_FLAGS=""

[mama21mama (mama21mama2000)]

was improved slightly.

mama@zeuza:~$ chromium-browser --proxy-server="https=localhost:31028;192.168.0.2:31028"
[9369:9418:325690073032:ERROR:x509_certificate_nss.cc(820)] CERT_PKIXVerifyCert for legadolibre.com.ar failed err=-8172

I do not like
failed err=-8172

[mama21mama (mama21mama2000)]

more info http://code.google.com/p/chromium/issues/detail?id=16830

[Paul White (paulw2u)]

@mama21mama, you last made comments to this bug report over 7 years ago.

The bug reports that you referred to were closed as being fixed. Can we now also close *this* bug report as also fixed?

[Paul White (paulw2u)]

I'm now closing this as fixed due to:

1) Upstream report was closed "Fixed (Closed)" on 2013/03/10
2) No response from reporter re comment #4
3) Issue has gone without comment for over 9 years