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

2020-12-08 Thread 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

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

2020-12-08 Thread 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

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

2020-12-08 Thread 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.

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

2020-12-08 Thread 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)

Re: [users@httpd] enforcing file transmission in gzip format with Apache 2.4.46

2020-12-08 Thread Ran Mozes
AddOutputFilter DEFLATE uar combined with 'IfSetEnv force-gzip‘ worked. Thanks! Ran > Am 02.12.2020 um 22:24 schrieb Christophe JAILLET > : > > Le 02/12/2020 à 16:59, a écrit : >> Hi, >> I'd like to configure the server to always send the requested *.uar files in >> gzip format back to