You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by David Reid <dr...@jetnet.co.uk> on 2001/01/22 19:52:10 UTC
Apache 2 URL...
Trying to download from this URL gives
http://bp6.cdws.com.au/
HTTP/1.1 400 Bad Request
Date: Mon, 22 Jan 2001 18:47:58 GMT
Server: Apache/2.0b1-dev (BeOS)
Content-Length: 401
Connection: close
Content-Type: text/html; charset=iso-8859-1
david
Re: Apache 2 URL...
Posted by "Guille (Bisho)" <gu...@eurielec.etsit.upm.es>.
> > I think we have a glitch somewhere. I tried to download one of the 2.3 meg files and got maybe 17K
> > then the connection goes down.
>
> We would need to know when they got the beta. I have served MANY meg's of
> data with the current HEAD. We would also need to know their platform.
The server was a BEOS machine I think..
Server: Apache/2.0b1-dev (BeOS)
--
\|||||||/ Guillermo Pérez Pérez
< o o > - bisho@onirica.com
\ L / - bisho@eurielec.etsit.upm.es
-oOOo-------oOOo-
Onírica: Análisis, diseño e implantación de soluciones informáticas
http://www.onirica.com
Re: Apache 2 URL...
Posted by Bill Stoddard <bi...@wstoddard.com>.
>
> > I think we have a glitch somewhere. I tried to download one of the 2.3 meg
files and got maybe 17K
> > then the connection goes down.
>
> We would need to know when they got the beta. I have served MANY meg's of
> data with the current HEAD. We would also need to know their platform.
>
It wouldn't suprise me of there are bugs in how Apache 2.0 (or APR) handles
partial writes or receiving EWOULDBLOCK.
The server runs through different code paths when serving content to a client
connected to the server over, say, a dial-up line that it does when serving to
a client connected on your local lan. The combination of a slow link with
high transit delays could be exposing a bug...
Bill
Re: Apache 2 URL...
Posted by rb...@covalent.net.
> I think we have a glitch somewhere. I tried to download one of the 2.3 meg files and got maybe 17K
> then the connection goes down.
We would need to know when they got the beta. I have served MANY meg's of
data with the current HEAD. We would also need to know their platform.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: Apache 2 URL...
Posted by Bill Stoddard <bi...@wstoddard.com>.
> On Tue, 23 Jan 2001, David Reid wrote:
>
> > Yeah sorry for not giving more info. Exam in the morning and so back to
> > normality soon...
> >
> > Basically whenever I try downloading from the sub directories I get errors
> > due to malformed URL's but I'm not sure if it's an apache problem or not...
> > Anyway, if people can download the mp3's then it's just my computer and
> > apache 2.0 doesn't have a problem, so fair enough... :) If not then maybe
> > we have a small glitch somewhere...
>
I think we have a glitch somewhere. I tried to download one of the 2.3 meg files and got maybe 17K
then the connection goes down.
Bill
Re: Apache 2 URL...
Posted by rb...@covalent.net.
> > This sounds like a problem I was having with 2.0a7. I was trying to get a
> > friend to d/l a file and he never could get it because it was too big.
>
> FWIW, I have been using 2.0a2-dev (mpmt_pthread.c) for my mp3
> collection[1] since march last year with no such problems. Very low
> traffic though (pretty much only myself).
In a2 we didn't have filter support, so that removes a big portion of the
logic.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: Apache 2 URL...
Posted by Ask Bjoern Hansen <as...@valueclick.com>.
On Tue, 23 Jan 2001, Austin Gonyou wrote:
> This sounds like a problem I was having with 2.0a7. I was trying to get a
> friend to d/l a file and he never could get it because it was too big.
FWIW, I have been using 2.0a2-dev (mpmt_pthread.c) for my mp3
collection[1] since march last year with no such problems. Very low
traffic though (pretty much only myself).
- ask
[1] SOP when I buy a new CD: 1) Convert to mp3. 2) Put CD in a box
somewhere and forget about it.
--
ask bjoern hansen - <http://ask.netcetera.dk/>
Re: Apache 2 URL...
Posted by Austin Gonyou <au...@coremetrics.com>.
This sounds like a problem I was having with 2.0a7. I was trying to get a
friend to d/l a file and he never could get it because it was too big. It
was like apache wouldn't allow more than x many bytes of transfer or
something. Also, a similar thing occurred if I whacked apache with AB
really hard. It would eventually accept connections but not return
anything.
--
Austin
On Tue, 23 Jan 2001, David Reid wrote:
> Yeah sorry for not giving more info. Exam in the morning and so back to
> normality soon...
>
> Basically whenever I try downloading from the sub directories I get errors
> due to malformed URL's but I'm not sure if it's an apache problem or not...
> Anyway, if people can download the mp3's then it's just my computer and
> apache 2.0 doesn't have a problem, so fair enough... :) If not then maybe
> we have a small glitch somewhere...
>
> Of course the fact that it's running a2 is cool as well :)
>
> david
>
> http://bp6.cdws.com.au/tmc/Filigree%20&%20Shadow/
>
> as an example...
>
> > >> > OK, the URL should be
> > >> >
> > >> > > >> >
> > >> > My bad.
> > >>
> > >> Oh?? I get a "200 OK", via Telnet to port 80 (HEAD, HTTP 1.0 and 1.1),
> and
> > >> with Lynx. What are you using??
> > >
> > >I think David was just saying that they were running 2.0b1-dev.
> >
> > I'm not sure:
> >
> > If you try this in your browser:
> > -------------------------------
> > http://bp6.cdws.com.au/images/screen1.png
> > The image don't load entirely
> >
> > Also, with wget you could see how the conection is closed at 32427 bytes
> each
> > time:
> > -------------------------------
> > $ wget http://bp6.cdws.com.au/images/screen1.png
> > --01:39:10-- http://bp6.cdws.com.au:80/images/screen1.png
> > => `screen1.png'
> > Connecting to bp6.cdws.com.au:80... connected!
> > HTTP request sent, awaiting response... 200 OK
> > Length: 175,674 [image/png]
> >
> > 0K -> .......... .......... .......... . [ 18%]
> >
> > 01:39:21 (3.26 KB/s) - Connection closed at byte 32427. Retrying.
> >
> > --01:39:21-- http://bp6.cdws.com.au:80/images/screen1.png
> > (try: 2) => `screen1.png'
> > Connecting to bp6.cdws.com.au:80... connected!
> > HTTP request sent, awaiting response... 206 Partial Content
> > Length: 175,674 (143,247 to go) [image/png]
> >
> > 0K -> ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,,, ,......... .......... [ 29%]
> > 50K -> .......... .. [ 36%]
> >
> >
>
Re: Apache 2 URL...
Posted by David Reid <dr...@jetnet.co.uk>.
Yeah sorry for not giving more info. Exam in the morning and so back to
normality soon...
Basically whenever I try downloading from the sub directories I get errors
due to malformed URL's but I'm not sure if it's an apache problem or not...
Anyway, if people can download the mp3's then it's just my computer and
apache 2.0 doesn't have a problem, so fair enough... :) If not then maybe
we have a small glitch somewhere...
Of course the fact that it's running a2 is cool as well :)
david
http://bp6.cdws.com.au/tmc/Filigree%20&%20Shadow/
as an example...
> >> > OK, the URL should be
> >> >
> >> > > >> >
> >> > My bad.
> >>
> >> Oh?? I get a "200 OK", via Telnet to port 80 (HEAD, HTTP 1.0 and 1.1),
and
> >> with Lynx. What are you using??
> >
> >I think David was just saying that they were running 2.0b1-dev.
>
> I'm not sure:
>
> If you try this in your browser:
> -------------------------------
> http://bp6.cdws.com.au/images/screen1.png
> The image don't load entirely
>
> Also, with wget you could see how the conection is closed at 32427 bytes
each
> time:
> -------------------------------
> $ wget http://bp6.cdws.com.au/images/screen1.png
> --01:39:10-- http://bp6.cdws.com.au:80/images/screen1.png
> => `screen1.png'
> Connecting to bp6.cdws.com.au:80... connected!
> HTTP request sent, awaiting response... 200 OK
> Length: 175,674 [image/png]
>
> 0K -> .......... .......... .......... . [ 18%]
>
> 01:39:21 (3.26 KB/s) - Connection closed at byte 32427. Retrying.
>
> --01:39:21-- http://bp6.cdws.com.au:80/images/screen1.png
> (try: 2) => `screen1.png'
> Connecting to bp6.cdws.com.au:80... connected!
> HTTP request sent, awaiting response... 206 Partial Content
> Length: 175,674 (143,247 to go) [image/png]
>
> 0K -> ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,,, ,......... .......... [ 29%]
> 50K -> .......... .. [ 36%]
>
>
Re: Apache 2 URL...
Posted by Guille -bisho- <bi...@eurielec.etsit.upm.es>.
>> > OK, the URL should be
>> >
>> > http://bp6.cdws.com.au/tmc/
>> >
>> > My bad.
>>
>> Oh?? I get a "200 OK", via Telnet to port 80 (HEAD, HTTP 1.0 and 1.1), and
>> with Lynx. What are you using??
>
>I think David was just saying that they were running 2.0b1-dev.
I'm not sure:
If you try this in your browser:
-------------------------------
http://bp6.cdws.com.au/images/screen1.png
The image don't load entirely
Also, with wget you could see how the conection is closed at 32427 bytes each
time:
-------------------------------
$ wget http://bp6.cdws.com.au/images/screen1.png
--01:39:10-- http://bp6.cdws.com.au:80/images/screen1.png
=> `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 175,674 [image/png]
0K -> .......... .......... .......... . [ 18%]
01:39:21 (3.26 KB/s) - Connection closed at byte 32427. Retrying.
--01:39:21-- http://bp6.cdws.com.au:80/images/screen1.png
(try: 2) => `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 206 Partial Content
Length: 175,674 (143,247 to go) [image/png]
0K -> ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,,, ,......... .......... [ 29%]
50K -> .......... .. [ 36%]
01:39:35 (2.39 KB/s) - Connection closed at byte 64237. Retrying.
--01:39:35-- http://bp6.cdws.com.au:80/images/screen1.png
(try: 3) => `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 206 Partial Content
Length: 175,674 (111,437 to go) [image/png]
[ skipping 50K ]
50K -> ,,,,,,,,,, ,,........ .......... .......... ... [ 54%]
01:39:47 (2.83 KB/s) - Connection closed at byte 96047. Retrying.
--01:39:47-- http://bp6.cdws.com.au:80/images/screen1.png
(try: 4) => `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 206 Partial Content
Length: 175,674 (79,627 to go) [image/png]
[ skipping 50K ]
50K -> ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,,, ,,,....... [ 58%]
100K -> .......... .......... .... [ 72%]
01:40:03 (2.90 KB/s) - Connection closed at byte 127858. Retrying.
--01:40:03-- http://bp6.cdws.com.au:80/images/screen1.png
(try: 5) => `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 206 Partial Content
Length: 175,674 (47,816 to go) [image/png]
[ skipping 100K ]
100K -> ,,,,,,,,,, ,,,,,,,,,, ,,,,...... .......... .......... [ 87%]
150K -> ..... [ 90%]
01:40:16 (2.56 KB/s) - Connection closed at byte 159668. Retrying.
--01:40:16-- http://bp6.cdws.com.au:80/images/screen1.png
(try: 6) => `screen1.png'
Connecting to bp6.cdws.com.au:80... connected!
HTTP request sent, awaiting response... 206 Partial Content
Length: 175,674 (16,006 to go) [image/png]
[ skipping 150K ]
150K -> ,,,,,..... .......... . [100%]
01:40:24 (2.28 KB/s) - `screen1.png' saved [175674/175674]
--
\|||||||/ Guillermo Pérez Pérez
< o o > - bisho@onirica.com
\ L / - bisho@eurielec.etsit.upm.es
-oOOo-------oOOo-
Onírica: Análisis, diseño e implantación de soluciones informáticas
http://www.onirica.com
Re: Apache 2 URL...
Posted by rb...@covalent.net.
On Mon, 22 Jan 2001, James Sutherland wrote:
> On Mon, 22 Jan 2001, David Reid wrote:
>
> > OK, the URL should be
> >
> > http://bp6.cdws.com.au/tmc/
> >
> > My bad.
>
> Oh?? I get a "200 OK", via Telnet to port 80 (HEAD, HTTP 1.0 and 1.1), and
> with Lynx. What are you using??
I think David was just saying that they were running 2.0b1-dev.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: Apache 2 URL...
Posted by James Sutherland <ja...@cam.ac.uk>.
On Mon, 22 Jan 2001, David Reid wrote:
> OK, the URL should be
>
> http://bp6.cdws.com.au/tmc/
>
> My bad.
Oh?? I get a "200 OK", via Telnet to port 80 (HEAD, HTTP 1.0 and 1.1), and
with Lynx. What are you using??
James.
Re: Apache 2 URL...
Posted by David Reid <dr...@jetnet.co.uk>.
OK, the URL should be
http://bp6.cdws.com.au/tmc/
My bad.
david
> Trying to download from this URL gives
>
> http://bp6.cdws.com.au/
>
> HTTP/1.1 400 Bad Request
> Date: Mon, 22 Jan 2001 18:47:58 GMT
> Server: Apache/2.0b1-dev (BeOS)
> Content-Length: 401
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
Re: Apache 2 URL...
Posted by James Sutherland <ja...@cam.ac.uk>.
On Mon, 22 Jan 2001, David Reid wrote:
> Trying to download from this URL gives
>
> http://bp6.cdws.com.au/
>
> HTTP/1.1 400 Bad Request
> Date: Mon, 22 Jan 2001 18:47:58 GMT
> Server: Apache/2.0b1-dev (BeOS)
> Content-Length: 401
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
Eeeeek. That's not what I get:
$ telnet bp6.cdws.com.au 80
HEAD / HTTP/1.0
HTTP/1.1 200 OK
Date: Mon, 22 Jan 2001 23:22:18 GMT
Server: Apache/2.0b1-dev (BeOS)
Last-Modified: Sat, 16 Dec 2000 06:41:48 GMT
ETag: "803b6-c8b-a4a00300"
Accept-Ranges: bytes
Content-Length: 3211
Connection: close
Content-Type: text/html; charset=ISO-8859-1
HTTP/1.1 200 OK
Date: Mon, 22 Jan 2001 23:22:18 GMT
Server: Apache/2.0b1-dev (BeOS)
Content-Length: 3211
Connection: close
Content-Type: text/html; charset=iso-8859-1
Connection closed by foreign host.
Is there something wrong with this picture?! (Aside: why the change of
case in the charset??)
James.