---
title: "Comment by mrcbns on \"Introduction to Cross Origin Resource Sharing (CORS)\" | Hashnode"
description: "Why can you await fetch whithout async first, which requires the use of immediately Invoked Function Expression? for example: ( async () =&gt; { const response"
url: "https://hashnode.com/posts/introduction-to-cross-origin-resource-sharing-cors/5f87c87bc5c9ff500d6cbb34/comment/5f87fb5b4aeeb354354ed1e5"
---

[Discussion](https://hashnode.com/posts/introduction-to-cross-origin-resource-sharing-cors/5f87c87bc5c9ff500d6cbb34)

Comment [Introduction to Cross Origin Resource Sharing (CORS)](https://hashnode.com/posts/introduction-to-cross-origin-resource-sharing-cors/5f87c87bc5c9ff500d6cbb34)

[mrcbns](https://hashnode.com/@mrcbns)

[Oct 15, 2020](https://hashnode.com/posts/introduction-to-cross-origin-resource-sharing-cors/5f87c87bc5c9ff500d6cbb34/comment/5f87fb5b4aeeb354354ed1e5)

Why can you _await fetch_ whithout async first, which requires the use of immediately Invoked Function Expression? for example:

```
(async () => {
    const response = await fetch('url&)
})()
```

[Victoria Lo](https://hashnode.com/@victoria)

[Oct 15, 2020](https://hashnode.com/posts/introduction-to-cross-origin-resource-sharing-cors/5f87c87bc5c9ff500d6cbb34/comment/5f87fb5b4aeeb354354ed1e5#reply-5f88d32cd7dc0b17a97a17c5)

Good question. CORS is server-side whereas fetching is from the client-side. CORS determines whether or not you are allowed to fetch from "[url".](https://url"./)
