Chrome 72+ seems to no longer accept --proxy-pac-url
I have an shortcut on several Windows PCs that points to Chrome with --proxy-pac-url.
Full Target: field in shortcut properties looks like this:
"C:Program Files (x86)GoogleChromeApplicationchrome.exe" --proxy-pac-url=file://C:/Local/Drive/Path/To/proxy.pac
One PC is always on and didn't restart Chrome in a long time. It still runs Chrome 71. On this PC .pac still works and I can access dynamically proxified resources. On the rest, where Chrome was updated to 72 and restarted it no longer works - Chrome tries to access resource directly and fails. Additionally, I can't debug it, since chrome://net-internals/#proxy shows is empty of any info save for re-apply/clear buttons.
So, what broke, how can I debug this and how to make a specific instance of Chrome run with specific .pac once again? Without always swapping options by hand, of course.
google-chrome proxy
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
add a comment |
I have an shortcut on several Windows PCs that points to Chrome with --proxy-pac-url.
Full Target: field in shortcut properties looks like this:
"C:Program Files (x86)GoogleChromeApplicationchrome.exe" --proxy-pac-url=file://C:/Local/Drive/Path/To/proxy.pac
One PC is always on and didn't restart Chrome in a long time. It still runs Chrome 71. On this PC .pac still works and I can access dynamically proxified resources. On the rest, where Chrome was updated to 72 and restarted it no longer works - Chrome tries to access resource directly and fails. Additionally, I can't debug it, since chrome://net-internals/#proxy shows is empty of any info save for re-apply/clear buttons.
So, what broke, how can I debug this and how to make a specific instance of Chrome run with specific .pac once again? Without always swapping options by hand, of course.
google-chrome proxy
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
add a comment |
I have an shortcut on several Windows PCs that points to Chrome with --proxy-pac-url.
Full Target: field in shortcut properties looks like this:
"C:Program Files (x86)GoogleChromeApplicationchrome.exe" --proxy-pac-url=file://C:/Local/Drive/Path/To/proxy.pac
One PC is always on and didn't restart Chrome in a long time. It still runs Chrome 71. On this PC .pac still works and I can access dynamically proxified resources. On the rest, where Chrome was updated to 72 and restarted it no longer works - Chrome tries to access resource directly and fails. Additionally, I can't debug it, since chrome://net-internals/#proxy shows is empty of any info save for re-apply/clear buttons.
So, what broke, how can I debug this and how to make a specific instance of Chrome run with specific .pac once again? Without always swapping options by hand, of course.
google-chrome proxy
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
I have an shortcut on several Windows PCs that points to Chrome with --proxy-pac-url.
Full Target: field in shortcut properties looks like this:
"C:Program Files (x86)GoogleChromeApplicationchrome.exe" --proxy-pac-url=file://C:/Local/Drive/Path/To/proxy.pac
One PC is always on and didn't restart Chrome in a long time. It still runs Chrome 71. On this PC .pac still works and I can access dynamically proxified resources. On the rest, where Chrome was updated to 72 and restarted it no longer works - Chrome tries to access resource directly and fails. Additionally, I can't debug it, since chrome://net-internals/#proxy shows is empty of any info save for re-apply/clear buttons.
So, what broke, how can I debug this and how to make a specific instance of Chrome run with specific .pac once again? Without always swapping options by hand, of course.
google-chrome proxy
google-chrome proxy
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
asked Feb 14 at 0:40
Oleg V. VolkovOleg V. Volkov
485318
485318
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Chrome removed almost all functionality of net-internals for some reason and it sounds like they removed the pac flag that you were using.
chromium docs link to this site that still lists the flag as valid.
https://peter.sh/experiments/chromium-command-line-switches/
answered Feb 14 at 15:28
SpyderzSpyderz
412
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' inchrome://flagsto go back to the old behaviour that supportsfile://pac files, though that will also be removed in future. Starting Chrome like/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkServicehas the same effect.
– paulcm
Feb 18 at 14:05
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405499%2fchrome-72-seems-to-no-longer-accept-proxy-pac-url%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Chrome removed almost all functionality of net-internals for some reason and it sounds like they removed the pac flag that you were using.
chromium docs link to this site that still lists the flag as valid.
https://peter.sh/experiments/chromium-command-line-switches/
answered Feb 14 at 15:28
SpyderzSpyderz
412
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' inchrome://flagsto go back to the old behaviour that supportsfile://pac files, though that will also be removed in future. Starting Chrome like/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkServicehas the same effect.
– paulcm
Feb 18 at 14:05
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
add a comment |
Chrome removed almost all functionality of net-internals for some reason and it sounds like they removed the pac flag that you were using.
chromium docs link to this site that still lists the flag as valid.
https://peter.sh/experiments/chromium-command-line-switches/
answered Feb 14 at 15:28
SpyderzSpyderz
412
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' inchrome://flagsto go back to the old behaviour that supportsfile://pac files, though that will also be removed in future. Starting Chrome like/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkServicehas the same effect.
– paulcm
Feb 18 at 14:05
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
add a comment |
Chrome removed almost all functionality of net-internals for some reason and it sounds like they removed the pac flag that you were using.
chromium docs link to this site that still lists the flag as valid.
https://peter.sh/experiments/chromium-command-line-switches/
answered Feb 14 at 15:28
SpyderzSpyderz
412
Chrome removed almost all functionality of net-internals for some reason and it sounds like they removed the pac flag that you were using.
chromium docs link to this site that still lists the flag as valid.
https://peter.sh/experiments/chromium-command-line-switches/
answered Feb 14 at 15:28
SpyderzSpyderz
412
edited Feb 14 at 15:37
answered Feb 14 at 15:28
SpyderzSpyderz
412
answered Feb 14 at 15:28
SpyderzSpyderz
412
answered Feb 14 at 15:28
SpyderzSpyderz
412
412
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' inchrome://flagsto go back to the old behaviour that supportsfile://pac files, though that will also be removed in future. Starting Chrome like/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkServicehas the same effect.
– paulcm
Feb 18 at 14:05
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
add a comment |
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' inchrome://flagsto go back to the old behaviour that supportsfile://pac files, though that will also be removed in future. Starting Chrome like/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkServicehas the same effect.
– paulcm
Feb 18 at 14:05
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
2
2
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
Here's the related Chromium issue where file:// PAC files were removed: bugs.chromium.org/p/chromium/issues/…
– paulcm
Feb 18 at 12:45
3
3
Also, as suggested in the bug, you can also disable 'Enable Network Service' in
chrome://flags to go back to the old behaviour that supports file:// pac files, though that will also be removed in future. Starting Chrome like /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkService has the same effect.– paulcm
Feb 18 at 14:05
Also, as suggested in the bug, you can also disable 'Enable Network Service' in
chrome://flags to go back to the old behaviour that supports file:// pac files, though that will also be removed in future. Starting Chrome like /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --disable-features=NetworkService has the same effect.– paulcm
Feb 18 at 14:05
1
1
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
@paulcm that should be an answer.
– Oleg V. Volkov
Feb 18 at 15:32
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405499%2fchrome-72-seems-to-no-longer-accept-proxy-pac-url%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
