# Httpc/httpd improvements

**URL:** <https://erlangforums.com/t/httpc-httpd-improvements/2622>\
**Category:** Proposals: Ideas\
**Tags:** httpd, erlang, inets, httpc\
**Created:** [May 21, 2023, 4:26pm UTC](https://erlangforums.com/t/httpc-httpd-improvements/2622 "2023-05-21T16:26:14Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![josevalim](https://erlangforums.com/user_avatar/erlangforums.com/josevalim/32/353_2.png) [@josevalim](https://erlangforums.com/u/josevalim)\
**Post date:** [May 25, 2023, 8:48am UTC](https://erlangforums.com/t/httpc-httpd-improvements/2622/7 "2023-05-25T08:48:00Z")

</div>

Hi @tsloughter 😃

I am generally of the opinion of having fewer applications as part of Erlang/OTP. With build tools and package managers available, I would leave concerns such as httpd to the community. 🙂

For httpc, I would focus on lower-level process-based abstractions. Think `gen_http`. This solves long-standing problems in other HTTP clients, which do impose an architecture and often end-up incurring additional performance costs (and more binary references). This is a design we explored with [Mint](https://github.com/elixir-mint/mint). You can still provide high-level functions that open up the connection and perform a request but without the pooling bits (which the community could build on top of).

> [@lpil](#):
>
> Another aspect that always confused me with httpc was how to correctly verify TLS.

I am almost sure this is the default and correctly done on Erlang/OTP 26.

---

_[View the full topic](https://erlangforums.com/t/httpc-httpd-improvements/2622)._
