Mailing List Archive: Cherokee: dev

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data.

Index | Next | Previous | View Threaded

codesite-noreply at google

Feb 17, 2009, 3:03 AM

Post #1 of 12 (447 views)
Permalink

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data.

Status: New
Owner: ----

New issue 365 by hanskanns: byte-range request offers a bad filesize
resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

What steps will reproduce the problem?

1. curl -o erlangen.bin --range 0-100000
http://ftp.uni-erlangen.de/pub/mirrors/opensuse/factory/iso/openSUSE-Factory-GNOME-LiveCD-i586-i686-Build0006-Media.iso
2. -rw------- 1 user users 100002 2009-02-16 20:18 erlangen.bin
3. But the correct size should be the following:
-rw------- 1 user users 100001 2009-02-16 20:20 widehat.bin
this is received with:
curl -o widehat.bin --range 0-100000
http://widehat.opensuse.org/factory/iso/openSUSE-Factory-GNOME-LiveCD-i586-i686-Build0006-Media.iso

What is the expected output? What do you see instead?

The filesize of the byte-range request, a.k.a. partial GET is one where the
client requests just a part of the file isn't correct. This is an optional
HTTP/1.1 feature and i think cherokee should be able to handle it.
I read in some lists that lighttpd in combination with ZFS has some similar
problems.

What version of the product are you using? On what operating system?

Cherokee 0.98.0
# uname -a
SunOS ftp 5.10 Generic_137112-08 i86pc i386 i86pc
#gcc -v
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/
configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --
with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --
enable-shared
Thread model: posix

Please provide any additional information below.

Maybe our ZFS is responsible for the error.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Feb 23, 2009, 3:14 AM

Post #2 of 12 (405 views)
Permalink

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Updates:
Labels: Type-Defect Priority-High Component-Logic

Comment #1 on issue 365 by alobbs: byte-range request offers a bad filesize
resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

Do you have some reference to those previous discussions? I'd like to read
them before I try to figure out what's
going on with the Cherokee+ZFS scenario.

Thanks!

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Feb 25, 2009, 5:20 AM

Post #3 of 12 (405 views)
Permalink

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #2 on issue 365 by hanskanns: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

ok sorry my first information was not completely correct ... it was a
problem with
zfs and last-modified-time in some lighttpd version ...
maybe it is not a zfs-related problem and you can test it without the zfs.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Feb 25, 2009, 5:34 AM

Post #4 of 12 (404 views)
Permalink

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #3 on issue 365 by alobbs: byte-range request offers a bad filesize
resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

That's weird. This is what I see at my side (on MacOS X):

=======
$ curl --range 0-100000 -o /tmp/tmp.cherokee http://localhost:1234/test.mp4
$ ls -l /tmp/tmp.cherokee
-rw-r--r-- 1 alo wheel 100001 Feb 25 14:30 /tmp/tmp.cherokee
=======

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Feb 25, 2009, 5:38 AM

Post #5 of 12 (404 views)
Permalink

Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #4 on issue 365 by alobbs: byte-range request offers a bad filesize
resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

The same on Linux:

=======
$ curl --range 0-100000 -o /tmp/tmp.cherokee2 http://ubuntu:1234/test.mp4
$ ls -l /tmp/tmp.cherokee*
-rw-r--r-- 1 alo wheel 100001 Feb 25 14:30 /tmp/tmp.cherokee
-rw-r--r-- 1 alo wheel 100001 Feb 25 14:34 /tmp/tmp.cherokee2
=======

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 1, 2009, 10:52 AM

Post #6 of 12 (109 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Updates:
Status: WaitingQA
Owner: skarcha
Cc: alobbs

Comment #16 on issue 365 by alobbs: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

I've just applied the patch:

http://svn.cherokee-project.com/changeset/3771

If everything works fine, it'll be shipped with Cherokee 0.99.27 within the
next few days.
*GREAT* job Antonio! :-)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 9, 2009, 11:24 PM

Post #7 of 12 (77 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #17 on issue 365 by hanskanns: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

really nice work.

curl -o erlangen.bin --range 0-100000
http://ftp.uni-erlangen.de/pub/mirrors/opensuse/distribution/11.1/iso/openSUSE-11.1-Addon-Lang-i586.iso
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 97k 100 97k 0 0 935k 0 --:--:-- --:--:-- --:--:--
1190k
-
4931603 104 -rw-r--r-- 1 cd cd 100001 2009-11-10 08:23
erlangen.bin

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 10, 2009, 12:12 AM

Post #8 of 12 (78 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Updates:
Status: Verified

Comment #18 on issue 365 by ste...@konink.de: byte-range request offers a
bad filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

Users happy, we happy! Thanks for the feedback.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 10, 2009, 7:25 AM

Post #9 of 12 (74 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #19 on issue 365 by hanskanns: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

ok new problem.

the above request which returns the correct size has been made with a curl
on debian4.0:
--
curl --version
curl 7.15.5 (i486-pc-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8c zlib/1.2.3
libidn/
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz
--

a second test on a solaris box returned the old -1byte size.
--
curl --version
curl 7.19.4 (i386-pc-solaris2.11) libcurl/7.19.4 OpenSSL/0.9.8a zlib/1.2.3
libidn/1.9
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

curl -o erlangen.bin --range 0-100000
http://ftp.uni-erlangen.de/pub/mirrors/opensuse/distribution/11.1/iso/openSUSE-11.1-Addon-Lang-i586.iso
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 97k 100 97k 0 0 1545k 0 --:--:-- --:--:-- --:--:--
1713k
xXx[at]solaris:~ 10 > ls -lisa erlangen.bin
32690215 224 -rw------- 1 xXx xXx 100000 Nov 10 16:15 erlangen.bin
--

what can we do now?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 10, 2009, 8:55 AM

Post #10 of 12 (74 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #20 on issue 365 by skarcha: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

Maybe because you are using Cherokee 0.99.24 on this server?

$ curl -I --range 0-100000 http://ftp.uni-
erlangen.de/pub/mirrors/opensuse/distribution/11.1/iso/openSUSE-11.1-Addon-Lang-
i586.iso
HTTP/1.1 206 Partial Content
Connection: Keep-Alive
Keep-Alive: timeout=15
Date: Tue, 10 Nov 2009 16:52:51 GMT
Server: Cherokee/0.99.24 (UNIX)
ETag: 493c651f=269c1000
Last-Modified: Mon, 08 Dec 2008 00:06:55 GMT
Content-Type: application/x-iso9660-image
Content-Range: bytes 0-100000/647761920
Content-Length: 100000

My server:

$ curl -I --range 0-100000 http://www.skarcha.com/ficheros/majazo.mpg
HTTP/1.1 206 Partial Content
Connection: Keep-Alive
Keep-Alive: timeout=15
Date: Tue, 10 Nov 2009 16:53:44 GMT
Server: Cherokee/0.99
ETag: 475583a4=19378
Last-Modified: Tue, 04 Dec 2007 16:43:16 GMT
Content-Type: video/mpeg
Content-Range: bytes 0-100000/103288
Content-Length: 100001

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 10, 2009, 2:53 PM

Post #11 of 12 (74 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #21 on issue 365 by hanskanns: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

sorry ... there was running still an old instance and the solaris box always
connected to that and the linux box connected to the other ...
now it looks fine.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 10, 2009, 3:00 PM

Post #12 of 12 (74 views)
Permalink

Re: Issue 365 in cherokee: byte-range request offers a bad filesize resuling in damaged data. [In reply to]

Comment #22 on issue 365 by skarcha: byte-range request offers a bad
filesize resuling in damaged data.
http://code.google.com/p/cherokee/issues/detail?id=365

No worries... Thanks a lot for all your feedback... ;)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com