# Http.net.bind.to vs http.bind.to

**URL:** <https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230>\
**Category:** Community\
**Created:** [November 12, 2024, 11:15am UTC](https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230 "2024-11-12T11:15:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gabriel](https://avatars.discourse-cdn.com/v4/letter/g/9de0a6/32.png) [@Gabriel](https://community.questdb.com/u/Gabriel)\
**Post date:** [November 12, 2024, 11:15am UTC](https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230/1 "2024-11-12T11:15:19Z")

</div>

Hello,

What is the difference between http.net.bind.to and http.bind.to?

My fundamental request is : can we block the console from an external IP while still allowing ILP over HTTP ?

Regards,  
Gabriel

---

<div class="post-metadata">

**Author:** ![Imre](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/imre/32/30_2.png) [@Imre](https://community.questdb.com/u/Imre)\
**Post date:** [November 12, 2024, 11:33am UTC](https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230/2 "2024-11-12T11:33:27Z")

</div>

Hi Gabriel,

_http.net.bind.to_ and _http.bind.to_ are the same settings, only the latter has been deprecated.  
Please, use _http.net.bind.to_.

Regarding blocking access to the web console from external IP addresses, I would use a firewall.  
You can let connections through to the ILP port, and block connections to the HTTP endpoint.

---

<div class="post-metadata">

**Author:** ![Gabriel](https://avatars.discourse-cdn.com/v4/letter/g/9de0a6/32.png) [@Gabriel](https://community.questdb.com/u/Gabriel)\
**Post date:** [November 12, 2024, 1:05pm UTC](https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230/3 "2024-11-12T13:05:19Z")

</div>

Thank you for the indication about those parameters.

AFAIK ILP over HTTP is using the same port as the HTTP web console and REST API. That’s where my problem starts. Ideally, I would like to allow the ILP over HTTP but not the console and neither the REST API.

---

<div class="post-metadata">

**Author:** ![Imre](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/imre/32/30_2.png) [@Imre](https://community.questdb.com/u/Imre)\
**Post date:** [November 12, 2024, 1:29pm UTC](https://community.questdb.com/t/http-net-bind-to-vs-http-bind-to/230/4 "2024-11-12T13:29:17Z")

</div>

Sorry, missed that you were talking about ILP over HTTP.

It is still doable, but you will have to setup rules on the firewall based on the request URI.

URI belongs to ILP over HTTP traffic:  
/write

URIs used by native InfluxDB clients (no need for these, unless you migrated from InfluxDB, and using their client to ingest data):  
/api/v2/write  
/ping

REST API endpoints:  
/exec  
/imp  
/exp

There are also other endpoints used by the Web Console (on top of the REST API), and monitoring tools such as Prometheus.

I think what you could setup a firewall rule to allow requests with **/write** , and disable everything else. That should make it possible to ingest data using ILP over HTTP coming from outside.