Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: supply .pac file via REST server #881

Open
echenley opened this issue Oct 28, 2019 · 2 comments
Open

Feature Request: supply .pac file via REST server #881

echenley opened this issue Oct 28, 2019 · 2 comments

Comments

@echenley
Copy link

echenley commented Oct 28, 2019

I am very new to Hoverfly, so apologies if this request is mildly incoherent. However, I could not find any existing issues that seemed relevant.

Is your feature request related to a problem? Please describe.

At my company, we are attempting to use Hoverfly to test features of an embedded app on production sites by swapping out the bundle when the Hoverfly proxy is active. Currently, we configure our corporate proxy using a .pac file. This PR added the ability to configure an upstream proxy via a pac file, which is great! However, in order to route requests in the browser (Chrome) through the hoverfly proxy, I need to update my proxy configuration via Mac network settings. Since we already use Automatic Proxy Configuration via a .pac file, it would be especially convenient to just switch to a .pac file created by the Hoverfly instance, rather than changing the proxy configuration method.

Describe the solution you'd like

Basically this:

Screen Shot 2019-10-28 at 5 14 59 PM

@echenley
Copy link
Author

echenley commented Oct 30, 2019

Found a way around this by opening chrome programmatically with the --proxy-server flag, which does not require changing system proxy settings.

open -na "Google Chrome" --args --proxy-server=http://localhost:8500

Leaving open for now in case this feature would be useful to others.

@JohnFDavenport
Copy link
Contributor

Thanks for letting us know @echenley. I will leave the issue open for further comment for the time-being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants