-
Notifications
You must be signed in to change notification settings - Fork 60.3k
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
Include work around for wildcards in HTTP Proxy Exclusion list on GHES #1502
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
github-actions
bot
added
the
triage
Do not begin working on this issue until triaged by the team
label
Nov 20, 2020
4 tasks
This comment has been minimized.
This comment has been minimized.
janiceilene
removed
the
triage
Do not begin working on this issue until triaged by the team
label
Dec 4, 2020
4 tasks
This was referenced Jul 31, 2022
This was referenced Jul 31, 2022
This was referenced Aug 1, 2022
jnidzwetzki
pushed a commit
to jnidzwetzki/docs
that referenced
this issue
Oct 6, 2022
* aiven-install * renamed the folder * updated the child pages * indented the child pages * indents, mostly * Trying with just a single page instead Co-authored-by: Lana Brindley <github@lanabrindley.com>
This was referenced Oct 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What article on docs.github.com is affected?
https://docs.github.com/en/enterprise-server@2.21/admin/configuration/configuring-an-outbound-web-proxy-server
What part(s) of the article would you like to see updated?
HTTP Proxy Exclusion.
The current instructions say to:
There is no mention of wildcards. However, if you enter
.mycompany.com
it will exclude any server ending with .mycompany.com ( this would include server.mycompany.com , web.mycompany.com, etc.mycompany.com, etc.)Additional information
This was mentioned by GitHub services. I have tested it and it works for me. We have been trying to fix this issue for over 4 years.
The text was updated successfully, but these errors were encountered: