
about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy
Preview meta tags from the about.gitlab.com website.
Linked Hostnames
19- 70 links toabout.gitlab.com
- 18 links togithub.com
- 7 links togitlab.com
- 3 links tohandbook.gitlab.com
- 2 links totwitter.com
- 2 links towww.facebook.com
- 2 links towww.linkedin.com
- 1 link tocourses.cs.vt.edu
Thumbnail

Search Engine Appearance
https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy
We need to talk: Can we standardize NO_PROXY?
Subtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
Bing
We need to talk: Can we standardize NO_PROXY?
https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy
Subtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
DuckDuckGo

We need to talk: Can we standardize NO_PROXY?
Subtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
General Meta Tags
7- titleWe need to talk: Can we standardize NO_PROXY?
- charsetutf-8
- viewportwidth=device-width, initial-scale=1
- Content-Security-Policydefault-src 'self' https: http:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https: http: *.googletagmanager.com *.mutinycdn.com; style-src 'self' 'unsafe-inline' https: http:; object-src https: http:; base-uri 'self'; connect-src 'self' https: http: wss: ws: *.google-analytics.com *.analytics.google.com *.googletagmanager.com *.mutinyhq.com *.mutinyhq.io *.mutinycdn.com; frame-src 'self' https: http:; img-src 'self' https: http: data: *.google-analytics.com *.googletagmanager.com *.mutinycdn.com; manifest-src 'self'; media-src 'self' https: http:; child-src 'self' blob: https: http:; font-src 'self' https: http: data:;
- format-detectiontelephone=no
Open Graph Meta Tags
7- og:typewebsite
- og:titleWe need to talk: Can we standardize NO_PROXY?
- og:descriptionSubtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
- og:imagehttps://res.cloudinary.com/about-gitlab-com/image/upload/v1749659507/Blog/Hero%20Images/AdobeStock_623844718.jpg
- og:urlhttps://about.gitlab.com/blog/we-need-to-talk-no-proxy
Twitter Meta Tags
6- twitter:cardsummary_large_image
- twitter:site@GitLab
- twitter:titleWe need to talk: Can we standardize NO_PROXY?
- twitter:imagehttps://res.cloudinary.com/about-gitlab-com/image/upload/v1749659507/Blog/Hero%20Images/AdobeStock_623844718.jpg
- twitter:descriptionSubtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
Link Tags
140- alternate/atom.xml
- alternate/all-releases.xml
- alternate/security-releases.xml
- alternate/releases.xml
- apple-touch-icon/images/ico/apple-touch-icon.png
Website Locales
8de
https://about.gitlab.com/de-de/blog/we-need-to-talk-no-proxy/de-de
https://about.gitlab.com/de-de/blog/we-need-to-talk-no-proxy/en
https://about.gitlab.com/blog/we-need-to-talk-no-proxy/en-us
https://about.gitlab.com/blog/we-need-to-talk-no-proxy/fr
https://about.gitlab.com/fr-fr/blog/we-need-to-talk-no-proxy/
Links
116- https://about.gitlab.com
- https://about.gitlab.com/ai-transparency-center
- https://about.gitlab.com/blog
- https://about.gitlab.com/blog/authors/stan-hu
- https://about.gitlab.com/blog/categories/engineering