-
Read RFC 2616 and implement response headers as described.
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead
In reality, not much significant has changed, but I want to highlight the new RFC's.
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…
-
```
I have some PDF-files I can't deliver with mongoose.
The http-header asks for something like
Range: bytes=581120-596717, 596718-606721, 606722-617449, 1836616-1837994,
1834896-1836229, 1844508-18…