You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Nikolaus Schlemm <ni...@cellity.com> on 2007/05/31 16:17:43 UTC
[AsyncWeb] chunked transfer coding
Hi,
Since I haven't received anything upon subscribing to the AsyncWeb mailinglist and I can't open a ticket for AsyncWeb on safehaus' jira, I'm posting this here although I'm not 100% sure this is the right place:
During a chunked transfer coding, if a chunk does not have an extension, the current implementation (from safehaus' svn) of ChunkedBodyDecodingState fails to decode the chunk correctly. Has anyone already encountered this? And possibly has a working patch? And where shall patches for AsyncWeb be posted atm?
Thanks in advance,
Nikolaus Schlemm
Senior Software Developer
cellity AG | Stahltwiete 23 | D-22761 Hamburg
Vorstand: Nils Weitemeyer (Vorstandsvorsitzender), Sarik Weber
Aufsichtsrat: Dr. Sven Claussen (Aufsichtsratzvorsitzender)
Handelsregistereintrag: HRB 99023, Amtsgericht Hamburg
Umsatzsteuer-Identnummer: DE251404018
BRANDNEU: Mit cellity freeSMS kostenlos SMS versenden! Hier ausprobieren http://www.cellity.com/freesms
Oder sofort per Handy runterladen: Sende „cellity“ an 86000
Re: [AsyncWeb] chunked transfer coding
Posted by hezjing <he...@gmail.com>.
Hi Nikolaus
Yes, I think we can discuss AsyncWeb here until the project is
migrated to MINA.
On 5/31/07, Nikolaus Schlemm <ni...@cellity.com> wrote:
> Hi,
>
> Since I haven't received anything upon subscribing to the AsyncWeb mailinglist and I can't open a ticket for AsyncWeb on safehaus' jira, I'm posting this here although I'm not 100% sure this is the right place:
>
> During a chunked transfer coding, if a chunk does not have an extension, the current implementation (from safehaus' svn) of ChunkedBodyDecodingState fails to decode the chunk correctly. Has anyone already encountered this? And possibly has a working patch? And where shall patches for AsyncWeb be posted atm?
>
> Thanks in advance,
>
> Nikolaus Schlemm
> Senior Software Developer
>
> cellity AG | Stahltwiete 23 | D-22761 Hamburg
>
> Vorstand: Nils Weitemeyer (Vorstandsvorsitzender), Sarik Weber
>
> Aufsichtsrat: Dr. Sven Claussen (Aufsichtsratzvorsitzender)
>
> Handelsregistereintrag: HRB 99023, Amtsgericht Hamburg
> Umsatzsteuer-Identnummer: DE251404018
>
> BRANDNEU: Mit cellity freeSMS kostenlos SMS versenden! Hier ausprobieren http://www.cellity.com/freesms
>
> Oder sofort per Handy runterladen: Sende „cellity" an 86000
>
--
Hez
Re: [AsyncWeb] chunked transfer coding
Posted by Trustin Lee <tr...@gmail.com>.
I applied the patch. Please let me know if it works or not.
Cheers,
Trustin
On 6/4/07, Nikolaus Schlemm <ni...@cellity.com> wrote:
> Hi,
>
> I hope I understood you right that you wanted this mailed to you personally?
>
> The attached patch is diffed against the latest AsyncWeb svn trunk and corrects the following points concerning http/1.1 chunked transfer coding:
>
> 1) when reading in the hexadecimal chunk size a chunk extension (marked by a semicolon) can optionally follow the size before a CRLF signals the start of the actual chunk data. The current AsyncWeb code treats this optional step as mandatory.
>
> 2) after the last (zero-sized) chunk a given number of trailers (each ended with their own CRLF) can optionally follow before a final CRLF signals the end of the transfer. The current AsyncWeb code looks for one CRLF too many, therefore the state AFTER_LAST_CHUNK_DATA is obsolete.
>
> In order to clarify the situation I've also attached a http request using chunks.
>
> Take care,
>
> Nikl
>
> > -----Ursprüngliche Nachricht-----
> > Von: Trustin Lee [mailto:trustin@gmail.com]
> > Gesendet: Freitag, 1. Juni 2007 09:16
> > An: dev@mina.apache.org
> > Betreff: Re: [AsyncWeb] chunked transfer coding
> >
> > On 5/31/07, Nikolaus Schlemm <ni...@cellity.com> wrote:
> > > Hi,
> > >
> > > Since I haven't received anything upon subscribing to the
> > AsyncWeb mailinglist and I can't open a ticket for AsyncWeb
> > on safehaus' jira, I'm posting this here although I'm not
> > 100% sure this is the right place:
> >
> > Please use this mailing list for now.
> >
> > > During a chunked transfer coding, if a chunk does not have
> > an extension, the current implementation (from safehaus' svn)
> > of ChunkedBodyDecodingState fails to decode the chunk
> > correctly. Has anyone already encountered this? And possibly
> > has a working patch? And where shall patches for AsyncWeb be
> > posted atm?
> >
> > Please e-mail me the patch cc'ing Dave for now.
> > Any example HTTP request that causes a problem will be appreciated.
> >
> > HTH,
> > Trustin
> > --
> > what we call human nature is actually human habit
> > --
> > http://gleamynode.net/
> > --
> > PGP Key ID: 0x0255ECA6
> >
> --
>
> Nikolaus Schlemm
> Senior Software Developer
>
> cellity AG | Stahltwiete 23 | D-22761 Hamburg
>
> Vorstand: Nils Weitemeyer (Vorstandsvorsitzender), Sarik Weber
>
> Aufsichtsrat: Dr. Sven Claussen (Aufsichtsratzvorsitzender)
>
> Handelsregistereintrag: HRB 99023, Amtsgericht Hamburg
> Umsatzsteuer-Identnummer: DE251404018
>
> BRANDNEU: Mit cellity freeSMS kostenlos SMS versenden! Hier ausprobieren http://www.cellity.com/freesms
>
> Oder sofort per Handy runterladen: Sende "cellity" an 86000
>
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: [AsyncWeb] chunked transfer coding
Posted by Trustin Lee <tr...@gmail.com>.
On 5/31/07, Nikolaus Schlemm <ni...@cellity.com> wrote:
> Hi,
>
> Since I haven't received anything upon subscribing to the AsyncWeb mailinglist and I can't open a ticket for AsyncWeb on safehaus' jira, I'm posting this here although I'm not 100% sure this is the right place:
Please use this mailing list for now.
> During a chunked transfer coding, if a chunk does not have an extension, the current implementation (from safehaus' svn) of ChunkedBodyDecodingState fails to decode the chunk correctly. Has anyone already encountered this? And possibly has a working patch? And where shall patches for AsyncWeb be posted atm?
Please e-mail me the patch cc'ing Dave for now.
Any example HTTP request that causes a problem will be appreciated.
HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6