Skip to content

Fix proxy documentation- * as wildcard is not supported#12463

Closed
bport wants to merge 2 commits into
docker:mainfrom
bport:patch-1
Closed

Fix proxy documentation- * as wildcard is not supported#12463
bport wants to merge 2 commits into
docker:mainfrom
bport:patch-1

Conversation

@bport

@bport bport commented Mar 9, 2021

Copy link
Copy Markdown

Proposed changes

Updated proxy documentation
According to documentation we can use * as a wild card for noProxy, this is not working.
And according to https://www.gnu.org/software/wget/manual/html_node/Proxies.html we need to prefix with a dot.

Related issue

#9745

@netlify

netlify Bot commented Mar 9, 2021

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 938fc67
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/6262a2e8b27c750008e8376e
😎 Deploy Preview https://deploy-preview-12463--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@usha-mandya usha-mandya requested a review from thaJeztah March 9, 2021 14:29
@usha-mandya usha-mandya added the area/networking Relates to anything around networking label Mar 9, 2021
@thaJeztah thaJeztah self-assigned this Mar 31, 2021
Comment thread network/proxy.md Outdated
usha-mandya
usha-mandya previously approved these changes Apr 22, 2022
Comment thread network/proxy.md
Comment on lines 29 to +27
You can optionally exclude hosts or ranges from going through the proxy
server by setting a `noProxy` key to one or more comma-separated IP
addresses or hosts. Using the `*` character as a wildcard for hosts and using CIDR notation for IP addresses is supported as
addresses or hosts. Prefixing domain with a dot `.` acts as a wildcard for hosts and using CIDR notation for IP addresses is supported as

@thaJeztah thaJeztah Apr 22, 2022

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm.. yes, these are "complicated", as the supported formats are not formalised. Perhaps we should mention something about that (supported formats depend on the software that's using the NO_PROXY (and other _PROXY/ _proxy vars), and we could link to the Go documentation, and possibly copy some of that; https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config

NoProxy represents the NO_PROXY or no_proxy environment
variable. It specifies a string that contains comma-separated values
specifying hosts that should be excluded from proxying. Each value is
represented by an IP address prefix (1.2.3.4), an IP address prefix in
CIDR notation (1.2.3.4/8), a domain name, or a special DNS label (*).
An IP address prefix and domain name can also include a literal port
number (1.2.3.4:80).
A domain name matches that name and all subdomains. A domain name with
a leading "." matches subdomains only. For example "foo.com" matches
"foo.com" and "bar.foo.com"; ".y.com" matches "x.y.com" but not "y.com".
A single asterisk (*) indicates that no proxying should be done.

I seem to recall we did that somewhere (but it could be I started working on it, but never pushed a PR 🤔)

@thaJeztah

Copy link
Copy Markdown
Member

Looks like this needs a rebase; otherwise this looks good to me (we can look at the improvements in a follow-up)

bport and others added 2 commits April 22, 2022 14:42
According to documentation we can use * as a wild card for noProxy, this is not working.
And according to https://www.gnu.org/software/wget/manual/html_node/Proxies.html we need to prefix with a dot.
@bport

bport commented Apr 22, 2022

Copy link
Copy Markdown
Author

Looks like this needs a rebase; otherwise this looks good to me (we can look at the improvements in a follow-up)

rebase done

@bport

bport commented Jul 26, 2022

Copy link
Copy Markdown
Author

@thaJeztah can we already merge this version ?

@docker-robott

Copy link
Copy Markdown
Collaborator

Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions.
As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.

If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.

Prevent pull requests from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

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

Labels

area/networking Relates to anything around networking lifecycle/stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants