You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/guides/concepts/ipfs-gateway.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -73,8 +73,11 @@ The discussion above illustrated the use of read-only HTTP(S) gateways to fetch
73
73
74
74
75
75
## 4. When should a gateway be provided, where, and which type of gateway?
76
-
<!-- Generic use cases -->
77
-
<!-- Which kind of gateway should be used when -->
76
+
77
+
### 4.1 Firewalled networks
78
+
Running [IPFS Desktop](https://github.com/ipfs-shipyard/ipfs-desktop#ipfs-desktop) or a standalone IPFS node within a browser/tool triggers connection attempts to other IPFS peers.
79
+
Private network administrations may treat such connection attempts as potential security vulnerabilities.
80
+
IPFS gateway servers inside the private network and running a trusted code base provide an alternative architecture for read/write access to externally-hosted IPFS content.
0 commit comments