# Making node respond as ipfs.io when getting files

**URL:** <https://discuss.ipfs.tech/t/making-node-respond-as-ipfs-io-when-getting-files/7251>\
**Category:** Help\
**Tags:** go-ipfs, files\
**Created:** [February 12, 2020, 2:35pm UTC](https://discuss.ipfs.tech/t/making-node-respond-as-ipfs-io-when-getting-files/7251 "2020-02-12T14:35:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bragaz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/bragaz/32/3490_2.png) [@Bragaz](https://discuss.ipfs.tech/u/Bragaz)\
**Post date:** [February 12, 2020, 2:35pm UTC](https://discuss.ipfs.tech/t/making-node-respond-as-ipfs-io-when-getting-files/7251/1 "2020-02-12T14:35:10Z")

</div>

Hi all! I’ve set up an ipfs node on AWS, and expose a public IP to allow third party apps to contact the REST API server (only for get/post requests) linked to our node (this is just an early stage choice).  
Well my question is pretty simple but I don’t know if the answer will be as well.  
Suppose that I add a file to ipfs and later want to cat it.  
Actually, what I can do is using the following query:

ipfs.desmos.network/api/v0/cat?arg=#hash

but I see that from [ipfs.io](http://ipfs.io), files can be retrieved as follow:

ipfs.io-ipfs-#hash

(i’m using - instead of / cause i’m a new user and I can’t post two links)

My question is, Can I set up the node to do the same things done with [ipfs.io](http://ipfs.io)?  
Is that a pre built feature? Or it is some mid-layer?  
Thanks to everyone who will answer in advance!

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [February 13, 2020, 12:16pm UTC](https://discuss.ipfs.tech/t/making-node-respond-as-ipfs-io-when-getting-files/7251/2 "2020-02-13T12:16:17Z")

</div>

Hi,

the `go-ipfs` daemon runs two things: one API (on tcp/5001 normally, with /api/v0/… endpoints) and one Gateway (on tcp/8080 normally). [ipfs.io](http://ipfs.io) is exposing the gateway part of it, which understands the /ipfs/hash paths.

> <https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#gateway>
