Re: [users@httpd] Changing the 'Range' inside the RequestHeader on the fly

[Ran Mozes]

Thanks!. After removing the "early“ it worked as expected. 

Regards,
Ran   

> Am 08.12.2020 um 16:52 schrieb Yann Ylavic :
> 
> On Tue, Dec 8, 2020 at 12:18 PM Ran Mozes  wrote:
>> 
>> RequestHeader edit Range bytes=\s bytes= early
> 
> I'm surprised this one doesn't work though.
> 
> Could it be that there are multiple spaces, or a space before the '=' sign 
> too?
> I.e. doesn't:
>  RequestHeader edit* Range ((\s+=)|(=\s+)) = early
> work better?
> 
> 
> Regards;
> Yann.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Changing the 'Range' inside the RequestHeader on the fly

[Yann Ylavic]

On Tue, Dec 8, 2020 at 12:18 PM Ran Mozes  wrote:
>
> RequestHeader edit Range bytes=\s bytes= early

I'm surprised this one doesn't work though.

Could it be that there are multiple spaces, or a space before the '=' sign too?
I.e. doesn't:
  RequestHeader edit* Range ((\s+=)|(=\s+)) = early
work better?


Regards;
Yann.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Changing the 'Range' inside the RequestHeader on the fly

[Yann Ylavic]

On Tue, Dec 8, 2020 at 12:18 PM Ran Mozes  wrote:
>
>
> http_request.c(440): [client 10.xxx.xxx.xx:x]   Range: bytes= 
> 7168-414976430
>
> Looks like this causes to fail serve the request.

Which error exactly does the log show ?


Regards;
Yann.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] Changing the 'Range' inside the RequestHeader on the fly

[Ran Mozes]

Hi,

Starting with with Apache 2.4.44 a strict check of the values given in the 
‚Range‘ header was introduced. The new change seems to not allow a blank after 
'bytes=' .
Unfortunately we have some faulty client that inserts an empty space after 
‚bytes=' (from apache error log) 

http_request.c(440): [client 10.xxx.xxx.xx:x]   Range: bytes= 
7168-414976430

Looks like this causes to fail serve the request.
 
Is it possible to work around this through the apache configuration, till the 
client will be fixed, by changing the ‚Range‘ header on the fly (get rid of the 
whitespace)?

I tried
Header edit Range bytes=\s bytes= early
and
RequestHeader edit Range bytes=\s bytes= early

but that didn’t work. 

Thanks,
Ran