Hi Adrian,
Can you provide a sample to reproduce this issue.
Thanks,
Hubert
On Tue, Dec 8, 2009 at 9:36 AM, <adrian.p.smith_at_bt.com> wrote:
> I notice that Grizzly rejects requests with more than one Content-Length
>
> header.
>
>
>
> I understand why this is done, but could the team consider an
>
> alternative strategy?
>
>
>
> Could the server be made to accept these requests, providing the values
>
> for content-length are identical?
>
>
>
> I have some legacy clients that I cannot change and this is making it
>
> hard for me to choose Grizzly as my prefered server.
>
>
>
> TIA.