Re: Which module is affected by the Range header issue?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: users@xxxxxxxxxxxxxxxx
Subject: Re: Which module is affected by the Range header issue?
From: Steve Foster <stephenfoster1971@xxxxxxxxx>
Date: Tue, 30 Aug 2011 16:44:57 +0100
In-reply-to: <CAO_cPBt75254eS8WWcCYcPTVsGvC4paGpbBXMxjkA1Gcy6xRXQ@mail.gmail.com>
Reply-to: users@xxxxxxxxxxxxxxxx

Correction , the static file gives a 206 status code...

On Tue, Aug 30, 2011 at 4:14 PM, Steve Foster <stephenfoster1971@xxxxxxxxx> wrote:

Hi eric,

yes i have tried it on a static file as well and no issues., obviously the static file gives a 200 status code back in the logs, but i am still sending the Range header as per the kill script

Follow-Ups:
- Re: Which module is affected by the Range header issue?
  - From: Steve Foster

References:
- Which module is affected by the Range header issue?
  - From: Steve Foster
- Re: Which module is affected by the Range header issue?
  - From: Eric Covener
- Re: Which module is affected by the Range header issue?
  - From: Steve Foster
- Re: Which module is affected by the Range header issue?
  - From: Eric Covener
- Re: Which module is affected by the Range header issue?
  - From: Steve Foster

Prev by Date: Re: Which module is affected by the Range header issue?
Next by Date: Re: Password access except localhost
Previous by thread: Re: Which module is affected by the Range header issue?
Next by thread: Re: Which module is affected by the Range header issue?
Index(es):
- Date
- Thread

[Index of Archives] [Open SSH Users] [Linux ACPI] [Linux Kernel] [Linux Laptop] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Squid] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper]

Powered by Linux