# Writable Gateway Specification

**URL:** <https://discuss.ipfs.tech/t/writable-gateway-specification/15616>\
**Category:** Protocol\
**Created:** [December 4, 2022, 4:48am UTC](https://discuss.ipfs.tech/t/writable-gateway-specification/15616 "2022-12-04T04:48:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![exxjob](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/exxjob/32/7218_2.png) [@exxjob](https://discuss.ipfs.tech/u/exxjob)\
**Post date:** [December 4, 2022, 4:48am UTC](https://discuss.ipfs.tech/t/writable-gateway-specification/15616/1 "2022-12-04T04:48:07Z")

</div>

According to [this conversation](https://github.com/ipfs/public-gateway-checker/pull/318#pullrequestreview-1144857294), a “comprehensive ingestion endpoint that goes beyond basic UnixFS” is needed for describing gateway writability.  
What’s the status / direction of this issue?

---

<div class="post-metadata">

**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\
**Post date:** [December 4, 2022, 12:53pm UTC](https://discuss.ipfs.tech/t/writable-gateway-specification/15616/2 "2022-12-04T12:53:41Z")

</div>

There are so many different ways to accomplish this.  
One such way, that would in theory be super applicable, is through WebDAV support. You can read all about that on my blog post [IPFS over WebDAV | IPFS Blog & News](https://blog.ipfs.tech/2022-10-13-ipfs-over-webdav/) feel very free to leave feedback!

There are many other different ways of accomplishing similar results.

Another lurking problem in “writable gateways” is how to handle permissions. For example, surely you don’t want every user from this forum using your gateway as their storage for multi-gigabyte-cat-videos, right 😉 So there needs to be a form of a permission model that allows “you” to add files, but not “the world”.

---

<div class="post-metadata">

**Author:** ![exxjob](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/exxjob/32/7218_2.png) [@exxjob](https://discuss.ipfs.tech/u/exxjob)\
**Post date:** [December 4, 2022, 9:12pm UTC](https://discuss.ipfs.tech/t/writable-gateway-specification/15616/3 "2022-12-04T21:12:29Z")

</div>

@markg85 honestly cat videos doesn’t sound bad

---

<div class="post-metadata">

**Author:** ![exxjob](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/exxjob/32/7218_2.png) [@exxjob](https://discuss.ipfs.tech/u/exxjob)\
**Post date:** [December 5, 2022, 7:54am UTC](https://discuss.ipfs.tech/t/writable-gateway-specification/15616/4 "2022-12-05T07:54:13Z")

</div>

I saw the article earlier, now read through it and the comments.  
It looks an interesting idea in establishing an IPFS norm.

Though I divert the topic: I’m focusing on a bare-bones gateway checker (foreign gateways) and I just want to detect it correctly. The convo gave impression that the method is potentially discouraged in far sight. I’m specifically looking at out-of-the-box access, ideally catch all cases and not be broken by implementations, iterations, or instances (compliant).  
This is what I mean to ask proper, likely depends on a consensus by PLabs.  
Thanks for the response