# HTTP Proxy ## HTTP Proxy Fluent Bit supports setting up a HTTP proxy for all egress HTTP/HTTPS traffic by setting `HTTP_PROXY` environment variable: * You can set up basic authentication with `HTTP_PROXY=http://:@:` to provide your `username` and `password` when connecting to the proxy. * You can also set up `HTTP_PROXY=http://:` to omit `username` and `password` if there is none. The `HTTP_PROXY` environment variable is a [standard way](https://docs.docker.com/network/proxy/#use-environment-variables) for setting a HTTP proxy in a containerized environment, and it is also natively supported by any application written in Go. Therefore, we follow and implement the same convention for Fluent Bit. **Note**: HTTP proxy is also supported using the [HTTP output plugin](https://docs.fluentbit.io/manual/pipeline/outputs/http). This configuration continues to work, however it *should not* be used together with the `HTTP_PROXY` environment variable. This is because under the hood, the `HTTP_PROXY` environment variable based proxy support is implemented by setting up a TCP connection tunnel via [HTTP CONNECT](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT). Unlike the plugin's implementation, this supports both HTTP and HTTPS egress traffic. ## NO\_PROXY In some environments, we wish HTTP traffic for some domains don't go through the HTTP\_PROXY, and this is where we need to use `NO_PROXY` environment variable. `NO_PROXY` is a comma-separated list of host names that shouldn't go through any proxy is set in (only an asterisk, \* matches all hosts), e.g. `foo.com,bar.com`. This is as a [curl convention](https://curl.se/docs/manual.html). One typical use case for `NO_PROXY` is when running fluent-bit in a Kubernetes environment, where we want: * All real egress traffic goes through a HTTP proxy. * All "Kubernetes local" traffic does not go through the HTTP proxy. * We can set `NO_PROXY=127.0.0.1,localhost,kubernetes.default.svc` in this case. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fluentbit.io/manual/1.8/administration/http-proxy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.