Actions
Bug #845
closedwhen storage for mod_compress module is almost full content is not completed
Status:
Fixed
Priority:
High
Category:
mod_compress
Target version:
-
ASK QUESTIONS IN Forums:
Description
I've done some lighttpd test
soymo@lusia ~/tests $ df --sync (...) /home/users/soymo/ext2.img 15863 1111 13933 8% /tmp/lighttpd soymo@lusia ~/tests $ printf 'GET /2.jpg HTTP/1.0\r\nAccept-Encoding: gzip\r\n\r\n' | nc localhost 80 | perl -e 'while(<STDIN>) { if(++$i>15) { print } }' > 2.jpg.gz ; file 2.jpg.gz ; gunzip 2.jpg.gz; file 2.jpg 2.jpg.gz: gzip compressed data, from Unix 2.jpg: JPEG image data, EXIF standard 2.2 soymo@lusia ~/tests $ printf 'GET /3.jpg HTTP/1.0\r\nAccept-Encoding: gzip\r\n\r\n' | nc localhost 80 | perl -e 'while(<STDIN>) { if(++$i>15) { print } }' > 3.jpg.gz ; file 3.jpg.gz ; gunzip 3.jpg.gz; file 3.jpg 3.jpg.gz: gzip compressed data, from Unix gunzip: 3.jpg.gz: unexpected end of file 3.jpg: cannot open `3.jpg' (No such file or directory) soymo@lusia ~/tests $ df --sync (...) System plików bl. 1K B u?yte dost?pne %u?. zamont. na /home/users/soymo/ext2.img 15863 15044 0 100% /tmp/lighttpd
In this situation mozilla shows cutted image. Next file won't be compressed, but when you request again to this file (3.jpg) - it'll be cutted (mod_compress cache).
Lightttpd doesn't log any informtion about it in error.log.
You can use zcat to uncompress this data (gunzip -f don't work).
-- soymo
Updated by stbuehler about 17 years ago
- Status changed from New to Fixed
- Resolution set to duplicate
See #1150.
Actions
Also available in: Atom