3 ms·
Building an HTTP library myself, I have to disagree. I drop two things here to counterargue that HTTP is easy to parse: 206 multiple ranges (requests will not
by cookiengineer 5y ago
Building an HTTP library myself, I have to disagree.
I drop two things here to counterargue that HTTP is easy to parse: 206 multiple ranges (requests will not always be responded to, and ranges from servers are almost always invalid when resumed) and Transfer Encodings (br inside gzip inside deflate inside chunked, anyone?)
Both headers are implemented spec incompliant by every single web server I've seen, including nginx, apache and others.
Source: building a peer to peer web browser that shares its bandwidth (and cache and downloads) with trusted peers. [1]
[1] https://github.com/tholian-network/stealth https://github.com/tholian-network/stealth