Open dentarg opened 8 years ago
Noticed how Slack does it
52.90.38.136 - - [15/May/2016:20:22:05 +0200] "GET /foo.txt HTTP/1.1" 206 3280 "-" "Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)"
52.90.146.42 - - [15/May/2016:20:22:05 +0200] "GET /foo.txt HTTP/1.1" 416 206 "-" "Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)"
http://stackoverflow.com/questions/8293687/sample-http-range-request-session https://benramsey.com/blog/2008/05/206-partial-content-and-range-requests/ https://en.wikipedia.org/wiki/Byte_serving https://httpstatuses.com/206 https://httpstatuses.com/416
Noticed how Slack does it
From a http://requestb.in/ (http://requestb.in/198y8vi1?inspect)
http://requestb.in
GET /198y8vi1
HEADERS
Accept-Encoding: gzip,deflate
Cache-Control: max-age=259200
Total-Route-Time: 0
Host: requestb.in
Accept: */*
User-Agent: Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)
X-Request-Id: 35b21545-31ae-47f2-93a0-388fde240aa0
Range: bytes=0-4096
Connect-Time: 1
Via: 1.1 vegur
Connection: close
FORM/POST PARAMETERS
None
RAW BODY
None
Or was it the fact that I posted another URL when it was working with the first one?
The offline tester handled the large file
I have to test for real, locally