On Sun, 2017-02-26 at 21:00 +0300, Basin Ilya wrote:
> Instead of writing data in my handler can I create there a custom bucket, let
> the byterange filter split it properly and let the core filter call my custom
> read function?
I think so in principle. Your bucket type would have to
satisfy
Hi Stefan,
currently everything fine. No segfaults.
Stefan
Am 25.02.2017 um 20:40 schrieb Stefan Priebe - Profihost AG:
> Hi Stefan,
> Am 25.02.2017 um 13:51 schrieb Stefan Eissing:
>> Stefan,
>>
>> whenever you have time, please deploy
>> https://github.com/icing/mod_h2/releases/tag/v1.9.2
>>
Instead of writing data in my handler can I create there a custom bucket, let
the byterange filter split it properly and let the core filter call my custom
read function?
On 26.02.2017 15:23, Nick Kew wrote:
> On Sun, 2017-02-26 at 15:02 +0300, Basin Ilya wrote:
>
>> However, it's inefficient
On Sun, 2017-02-26 at 15:02 +0300, Basin Ilya wrote:
> However, it's inefficient to serve huge virtual files this way when only a
> small part of such file requested. How to solve this?
Unless your module can handle the byterange itself, you might
want to consider cacheing the generated file
Hi.
I have a custom module that generates its output on the fly. (Consider a
hypothetical "download.cgi" or "download.php", but it's a module, not script).
I don't process the range headers myself. I just write the whole data using
ap_rwrite(). If the client performs a ranged request, the
