At 03:41 AM 8/28/2002, Peter Van Biesen wrote:
>As far as I can see, no ranges supplied. I've downloaded a 'small file'
>with my browser :
>
>193.53.20.83 - - [28/Aug/2002:10:33:25 +0200] "-" "GET
>http://hpux.cs.utah.edu/ftp/hpux/Gnu/gdb-5.2.1/gdb-5.2.1-sd-11.00.depot.gz
>HTTP/1.1" 200 7349572
>
>the "-" is the range.
>
>Since the child crashes, nothing gets written in the access log, but I
>added code to print out the headers :
Hmmm. I was asking about the client-request headers, not the server
response headers. But no matter, this doesn't appear to be the problem.
It's definitely not the same problem as byteranges-not-handled-correctly
by mod_proxy. I'm going to take a wild stab that you may simply be
running out of memory?
>[Wed Aug 28 10:30:04 2002] [debug] proxy_util.c(444): proxy: headerline
>= Transfer-Encoding: chunked
>[Wed Aug 28 10:30:04 2002] [debug] proxy_http.c(893): proxy: start body
>send
>[Wed Aug 28 10:36:23 2002] [notice] child pid 7534 exit signal
>Segmentation fault (11)
>
>I'm installing gdb, as you can see ;-)
>
>Peter.
>
>"William A. Rowe, Jr." wrote:
> >
> > At 07:53 AM 8/27/2002, Peter Van Biesen wrote:
> > >What should I call it then ? not-so-tiny-files ? 8-)
> >
> > Nah... large or big files is just fine :-)
> >
> > I'm guessing $$$s to OOOs [donuts] that your client is starting
> > some byteranges somewhere along the way. Try adding the bit
> > \"%{Range}i\" in one of your access log formats to see if this is
> > the case.
> >
> > As I understand it today, proxy plus byteranges is totally borked.
> >
> > Bill
