-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Full Support For Environment Proxy (http, https, no_proxy) #73
base: master
Are you sure you want to change the base?
Conversation
b1e06ab
to
72e5725
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't comment every place that needs review but the pattern exists throughout the code and is covered in a few of the comments. I'll do a deeper review once we get the initial syntax in order
Reflecting Dockerfile-netbootxyz changes. Split the `start.sh` entrypoint file: - init.sh - prepares environment and directories on first run - start.sh - entrypoint script that runs supervisord and init.sh Made basic set of parameters (ports) configurable. Now the `default` file need to be templated before first run. Minor fixes due to supervisor failing. Added proxy settings from environment pass to WebApplication Signed-off-by: Milosz Linkiewicz <[email protected]>
HTTP and HTTPS proxy agents added. Now every link connection before cration is checked against environment variables: - http_proxy/HTTP_PROXY, - https_proxy/HTTPS_PROXY, - no_proxy/NO_PROXY, It is determined if connection should be routed throug proxy server. This includes: - DownloaderHelper. - Socket fetch. - Devgetbrowser method. Fix to Readdirp handling after migration to v4.0.0. Signed-off-by: Milosz Linkiewicz <[email protected]>
Dockerfile code improvements and labeles added. The improvements include using bash as default shell for bettter error detection while performing install and start of container. Signed-off-by: Milosz Linkiewicz <[email protected]>
I've changed it as you mentioned. IF you find some time I would be grateful for a review :). BTW the project if really awesome! |
Full http_proxy https_proxy, no_proxy suupport:
Support for http_proxy, https_proxyh and no_proxy environment variables implemented. This include reading variables from process environment, comparing request_url with no_proxy cidr's and names, and of course setting and redirecting requests using proxy or corporate proxy services. This does not impact by any means the DHCP and TFTP services - only webapp.
Environments read for comparision:
http_proxy
||HTTP_PROXY
https_proxt
||HTTPS_PROXY
no_proxy
||NO_PROXY
Implemented and/or extended:
One method for each approach getProxyAgentFromUrl().
Almost no changes to the code are needed.
This fully resolves: #66