Realistically, I would estimate end of August as a reasonable time frame.
Thursday, August 8, 2013, 7:36:43 PM, you wrote:
> I'm glad that the problem is at least known.
> Do you have a gut-feeling when you will find the time? Is it rather this
> month, in the next 3 months, this year or rather i
I'm glad that the problem is at least known.
Do you have a gut-feeling when you will find the time? Is it rather this
month, in the next 3 months, this year or rather in 2014?
Best Regards,
Sebastian
-Ursprüngliche Nachricht-
Von: Alan M. Carroll [mailto:a...@network-geographics.com]
Gese
> > how about generating this from autoconf?
>
> We do, but readthedocs.org doesn't run the autoconf
huh? And there's no way to fix that?
> J
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097
On Aug 8, 2013, at 2:47 PM, Igor Galić wrote:
>
>
> - Original Message -
>> Updated Branches:
>> refs/heads/master c78a4f886 -> 3fad79d75
>>
>>
>> docs: update sphinx documentation version
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
>> Commit: http:/
The range transforms worked at for 3.0 but were broken for 3.2. This was masked
by the addition of range acceleration but when that was determined to be too
risky the original range transform issue was re-exposed. I'm currently trying
to get some time to work on that, I see what the problem is,
- Original Message -
> Updated Branches:
> refs/heads/master c78a4f886 -> 3fad79d75
>
>
> docs: update sphinx documentation version
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/3fad79d7
Hi,
So far I'm happy with everything except HTTP range requests.
Whenever the plugin is null-transforming a HTTP range request the
following is happening:
* the return code is set to 200 (instead of 206)
* the content-range header is omitted
* nevertheless the plugin only 'sees' the requested byt
- Original Message -
> On Aug 8, 2013, at 6:40 AM, Igor Galić wrote:
>
> >
> >
> > - Original Message -
> >>
> >>
> >> Hi folks,
> >>
> >> right now many of plugins send error messages without prefixing the plugin
> >> they come from, this bad practice is also continued in
On Aug 8, 2013, at 6:40 AM, Igor Galić wrote:
>
>
> - Original Message -
>>
>>
>> Hi folks,
>>
>> right now many of plugins send error messages without prefixing the plugin
>> they come from, this bad practice is also continued in our examples.
>>
>> many error messages also close w
+1
On Aug 8, 2013, at 6:40 AM, Igor Galić wrote:
>
>
> - Original Message -
>>
>>
>> Hi folks,
>>
>> right now many of plugins send error messages without prefixing the plugin
>> they come from, this bad practice is also continued in our examples.
>>
>> many error messages also clo
- Original Message -
> Updated Branches:
> refs/heads/master caf79a236 -> 1ddfc042f
>
>
> TS-1823: add line continuation to remap.config
>
> Add line continuation to remap.config using a backslash at the end
> of a line as the continuation character.
>
> The handling for continuatio
- Original Message -
>
>
> Hi folks,
>
> right now many of plugins send error messages without prefixing the plugin
> they come from, this bad practice is also continued in our examples.
>
> many error messages also close with `\n`, although this is not necessary.
>
> We should fix t
12 matches
Mail list logo