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

Thumbnail

Search Engine Appearance

Google

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

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.

  • General Meta Tags

    7
    • title
      We need to talk: Can we standardize NO_PROXY?
    • charset
      utf-8
    • viewport
      width=device-width, initial-scale=1
    • Content-Security-Policy
      default-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-detection
      telephone=no
  • Open Graph Meta Tags

    7
    • og:type
      website
    • og:title
      We need to talk: Can we standardize NO_PROXY?
    • og:description
      Subtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.
    • og:image
      https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659507/Blog/Hero%20Images/AdobeStock_623844718.jpg
    • og:url
      https://about.gitlab.com/blog/we-need-to-talk-no-proxy
  • Twitter Meta Tags

    6
    • twitter:card
      summary_large_image
    • twitter:site
      @GitLab
    • twitter:title
      We need to talk: Can we standardize NO_PROXY?
    • twitter:image
      https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659507/Blog/Hero%20Images/AdobeStock_623844718.jpg
    • twitter:description
      Subtle 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

    8
    • DE country flagde
      https://about.gitlab.com/de-de/blog/we-need-to-talk-no-proxy/
    • DE country flagde-de
      https://about.gitlab.com/de-de/blog/we-need-to-talk-no-proxy/
    • EN country flagen
      https://about.gitlab.com/blog/we-need-to-talk-no-proxy/
    • US country flagen-us
      https://about.gitlab.com/blog/we-need-to-talk-no-proxy/
    • FR country flagfr
      https://about.gitlab.com/fr-fr/blog/we-need-to-talk-no-proxy/

Links

116