# Asynchronous HTTP requests

**URL:** <https://forum.crystal-lang.org/t/asynchronous-http-requests/466>\
**Category:** Help & Support\
**Created:** [February 24, 2019, 12:33am UTC](https://forum.crystal-lang.org/t/asynchronous-http-requests/466 "2019-02-24T00:33:43Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![asterite](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/asterite/32/60_2.png) [@asterite](https://forum.crystal-lang.org/u/asterite)\
**Post date:** [February 24, 2019, 6:33pm UTC](https://forum.crystal-lang.org/t/asynchronous-http-requests/466/8 "2019-02-24T18:33:17Z")

</div>

> [while it behave exactly like await/async in Scala](https://github.com/scala/scala-async)

No, it doesn’t. Check the scala example. You are supposed to call `await` inside an `async` block. Then Scala probably rewrites the whole thing to continuations or something.

In your case you have `async`, which means `future`, and `await`, which means “wait for the future to complete and get its result”.

I still think that naming this `async`/`await` is not correct.

---

_[View the full topic](https://forum.crystal-lang.org/t/asynchronous-http-requests/466)._