On 4/15/13 4:35 PM, Leif Hedstrom wrote:
Hi all,
I've prepared a release for v3.3.2, which has quite a few improvements and
bug fixes over 3.3.0. Please see the CHANGES for more details. It's
important we get as much testing as possible for these dev releases for
the next few months, in prepa
We've been chasing a strange problem with an ironbee
test case. As the HTTP header size (from the method
to the blank line) grows above 4K, TSAPI 'loses' the
first 4Kb. Request line details (method, url, version)
are fine if we use their explicit APIs, but the data
are lost/
I'll attach a mini
On 4/19/13 4:54 AM, Igor Galić wrote:
It's a compiler warning rather than an error.
If you build without -Werror you probably wouldn't
notice the warnings as they scroll past.
We need a respin for this? Nick can you file a bug for this please?
respin?
I wouldn't treat it as fatal for a dev rel
> >
> > Well, it compiles and runs for me on my 32-bit platform :-/. I use
> > gcc
> > v4.7.0 on an old (RHEL4) 32-bit machine.
>
> Hmm, this is an older gcc:
>
> $ gcc --version
> gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
>
> It's a compiler warning rather than an error.
> If you build without -Wer
