Tested this issue on Mac 10.12.3 with chrome version #58.0.3018.3
From the mac console launched chrome with following argument --headless --proxy-server="http=127.0.0.1:80;https=127.0.0.1:443"

Chrome launched successfully and didn't observe any "Malformed proxy server url" in the Mac Console.

Could you please let us on Which OS you faced this issue, so that we can try to reproduce the scenario from TE-end.

Thank You...

I tested this on Linux (CentOS 7). It works correctly without the --headless flag but with the --headless flag it errors.

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce this issue on Ubuntu 14.04 on latest chrome Dev #58.0.3026.3
Issue is broken in M57.

Bisect Info:
===========
Good build : 57.0.2950.0,  Revision Range- 438011
Bad build  : 57.0.2951.0,  Revision Range- 438385

Unable to run the bisect script, since it is breaking with the given flag in comment #0

Looking at the changelog's between bisect range
---------------------------------------------------
https://chromium.googlesource.com/chromium/src/+log/57.0.2950.0..57.0.2951.0?pretty=fuller&n=10000

Suspecting Change Log:
----------------------
https://chromium.googlesource.com/chromium/src/+/b354f8865623b8ca8da43f7ef37332bdb586dd82

Review-Url: https://codereview.chromium.org/1991953002


skyostil@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.


Thank You...

Hi,

without sounding impolite, are there any updates as I am facing the same issue?

Thank you

I believe this issue is quite important. Headless mode is used for automation use cases. It is quite common to use a proxy in such cases.
This is blocked by this bug.

+1, I am blocked by this issue as well. Any ETA would be very helpful. 

Hi - Is this issue fixed. Even I am facing the same problem. There is no update on this ticket since long.