Range header is not syntactically valid
pmonks opened this issue · comments
As per RFC-2616 §14.35, the value of a "Range" header must include a range unit (e.g. "bytes"). Currently, the unfurl library is not doing this.
This library implements "URL unfurling" approximately according to how Slack does it.
pmonks opened this issue · comments
As per RFC-2616 §14.35, the value of a "Range" header must include a range unit (e.g. "bytes"). Currently, the unfurl library is not doing this.