# Filebeat http endpoint CORS

**URL:** <https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 28, 2021, 4:40am UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712 "2021-02-28T04:40:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![snowfrogdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/snowfrogdev/32/84655_2.png) [@snowfrogdev](https://discuss.elastic.co/u/snowfrogdev)\
**Post date:** [February 28, 2021, 4:40am UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712/1 "2021-02-28T04:40:19Z")

</div>

Is there any way to setup CORS when using Filebeat http\_endpoint?

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [March 1, 2021, 9:32am UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712/2 "2021-03-01T09:32:27Z")

</div>

I'm not convinced if it's possible to configure a simple/nice workaround. Could you please describe your use case?

---

<div class="post-metadata">

**Author:** ![snowfrogdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/snowfrogdev/32/84655_2.png) [@snowfrogdev](https://discuss.elastic.co/u/snowfrogdev)\
**Post date:** [March 1, 2021, 1:24pm UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712/3 "2021-03-01T13:24:48Z")

</div>

I'm building a little Proof of Concept / Prototype for introducing the Elk stack to our project. The idea is to be able to show the team what the elk stack can do for us. I'm not worried about implementing it properly and securely.

Right now I'm focusing on the Angular front-end logging. I'm trying to send log events from the Angular client to Filebeat's http\_endpoint as a quick and dirty way to get the logs to show up in Kibana. Obviously, with a real implementation, the logs will be sent through our API gateway. I was really hoping to be able to bypass having to implement all the stuff in between the client and Filebeat. http\_endpoint seemed like the perfect solution.

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [March 2, 2021, 9:53am UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712/4 "2021-03-02T09:53:52Z")

</div>

I'm afraid in this case you'll have to add proxy in front of filebeat that can handle CORS adequately.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 30, 2021, 11:54am UTC](https://discuss.elastic.co/t/filebeat-http-endpoint-cors/265712/5 "2021-03-30T11:54:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.