Created
March 2, 2017 17:53
-
-
Save NeoTeo/235b8e6b38edb214a56bc7368fcbe843 to your computer and use it in GitHub Desktop.
wireshark dump using ipfs client
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
POST /api/v0/add?encoding=json&progress=true&stream-channels=true HTTP/1.1 | |
Host: 127.0.0.1:5001 | |
User-Agent: /go-ipfs/0.4.6-dev/ | |
Connection: close | |
Transfer-Encoding: chunked | |
Content-Type: multipart/form-data; boundary=060868038e6ecedef3cd5968bc99c80d3cbe38194857f66747f07bc191bc | |
Accept-Encoding: gzip | |
1 | |
- | |
a0 | |
-060868038e6ecedef3cd5968bc99c80d3cbe38194857f66747f07bc191bc | |
Content-Disposition: file; filename="ipfssized-2.txt" | |
Content-Type: application/octet-stream | |
1322 | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high. | |
a1 | |
--060868038e6ecedef3cd5968bc99c80d3cbe38194857f66747f07bc191bc | |
Content-Disposition: file; filename="ipfssized.txt" | |
Content-Type: application/octet-stream | |
1322 | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage. | |
HTTP is inefficient and expensive | |
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs. | |
IPFS makes it possible to distribute high. | |
44 | |
--060868038e6ecedef3cd5968bc99c80d3cbe38194857f66747f07bc191bc-- | |
0 | |
HTTP/1.1 200 OK | |
Access-Control-Allow-Headers: X-Stream-Output, X-Chunked-Output, X-Content-Length | |
Access-Control-Expose-Headers: X-Stream-Output, X-Chunked-Output, X-Content-Length | |
Content-Type: application/json | |
Server: go-ipfs/0.4.6-dev | |
Trailer: X-Stream-Error | |
Vary: Origin | |
X-Chunked-Output: 1 | |
Date: Thu, 02 Mar 2017 17:51:52 GMT | |
Connection: close | |
Transfer-Encoding: chunked | |
28 | |
{"Name":"ipfssized-2.txt","Bytes":4898} | |
53 | |
{"Name":"ipfssized-2.txt","Hash":"QmUwDoyhv8Sr9sCt2uYgwHs3LcPcZwcqMwQ57C7YJV5SGG"} | |
26 | |
{"Name":"ipfssized.txt","Bytes":4898} | |
51 | |
{"Name":"ipfssized.txt","Hash":"QmUwDoyhv8Sr9sCt2uYgwHs3LcPcZwcqMwQ57C7YJV5SGG"} | |
0 | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment