# HTTP POST Outcalls

**URL:** <https://forum.dfinity.org/t/http-post-outcalls/33741>\
**Category:** Developers\
**Created:** [July 31, 2024, 7:55am UTC](https://forum.dfinity.org/t/http-post-outcalls/33741 "2024-07-31T07:55:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rbole](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rbole/32/1334_2.png) [@rbole](https://forum.dfinity.org/u/rbole)\
**Post date:** [July 31, 2024, 7:55am UTC](https://forum.dfinity.org/t/http-post-outcalls/33741/1 "2024-07-31T07:55:56Z")

</div>

I have a question regarding HTTP Outcalls. When I attempt to send a POST request to a web2 API, I encounter the following error. The first request works fine, but the subsequent requests fail. The key difference is that the first request takes some time to process, while the following requests are faster.

> The replica returned a rejection error: reject code CanisterReject, reject message Connecting to [xx.samlinux.com](http://xx.samlinux.com) failed: Failed to directly connect: error trying to connect: tcp connect error: Network is unreachable (os error 101), error code None

---

<div class="post-metadata">

**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\
**Post date:** [July 31, 2024, 1:37pm UTC](https://forum.dfinity.org/t/http-post-outcalls/33741/2 "2024-07-31T13:37:01Z")

</div>

> [@rbole](#):
>
> Failed to directly connect: error trying to connect: tcp connect error: Network is unreachable

Have you checked if the API supports [IPv6](https://internetcomputer.org/docs/current/references/https-outcalls-how-it-works#ipv6-only-support)?

---

<div class="post-metadata">

**Author:** ![rbole](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rbole/32/1334_2.png) [@rbole](https://forum.dfinity.org/u/rbole)\
**Post date:** [July 31, 2024, 2:03pm UTC](https://forum.dfinity.org/t/http-post-outcalls/33741/3 "2024-07-31T14:03:49Z")

</div>

Thanks for that info, but after a long day searching 🤒 I have also found this info into the docs.

No, currently the service doesn’t support IPv6. I have to find now a way to write my own service or configure the existing one if possible.

---

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [July 31, 2024, 2:16pm UTC](https://forum.dfinity.org/t/http-post-outcalls/33741/4 "2024-07-31T14:16:35Z")

</div>

> [@rbole](#):
>
> configure the existing one if possible

If it can be useful, few existing solutions listed there → [IPv6 support for HTTPS Outcalls - #2 by peterparker](https://forum.dfinity.org/t/ipv6-support-for-https-outcalls/32766/2)

---

<div class="post-metadata">

**Author:** ![rbole](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rbole/32/1334_2.png) [@rbole](https://forum.dfinity.org/u/rbole)\
**Post date:** [August 1, 2024, 6:40am UTC](https://forum.dfinity.org/t/http-post-outcalls/33741/5 "2024-08-01T06:40:34Z")

</div>

Thanks, @peterparker, for the links. I noticed your OpenAI proxy implementation. I followed a similar approach using Node.js.

In my example, I need to send from content as emails from a website. But I had to use a specific SMTP provider based in Austria.