You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment during enrollment the --header flag is only used for adding headers with communication with Elasticsearch, it is not used with communication with Fleet Server. The same --header flag should be used for communication with Fleet Server.
Why?
--header is normally used for reverse proxies that have some type of filtering enabled that doesn't allow a request to be proxied to the proper backend unless a specific header is present.
At the moment we support this for Elasticsearch, but not for communication with Fleet Server.
The text was updated successfully, but these errors were encountered:
Overview
At the moment during enrollment the
--header
flag is only used for adding headers with communication with Elasticsearch, it is not used with communication with Fleet Server. The same--header
flag should be used for communication with Fleet Server.Why?
--header
is normally used for reverse proxies that have some type of filtering enabled that doesn't allow a request to be proxied to the proper backend unless a specific header is present.At the moment we support this for Elasticsearch, but not for communication with Fleet Server.
The text was updated successfully, but these errors were encountered: