Re: Error in http.lua's chunked encoding

[Ron <ron () skullsecurity net>]

After troubleshooting an issue with why a couple strings wouldn't match, 
I noticed that one of them has an "EOF" on the end while the other 
doesn't (one pulled from http.get() and the other from http.pipeline()). 
I'm assuming this is related to the same issue, but I can give you more 
details about that if it helps.

(For now I just did a quick workaround, string.psub(str, "EOF", "") -- 
obviously *not* the right way)

Thanks!
ron

On 08/18/2009 08:29 PM, Joao Correa wrote:
> Nice catch David! Thanks a lot for elucidating me =).
>
> I'll start work on a better patch and I'll get in touch soon!
> Thanks,
> João.
>
> On Tue, Aug 18, 2009 at 3:47 PM, David Fifield<david () bamsoftware com>  wrote:
> > On Tue, Aug 18, 2009 at 12:35:25PM -0600, David Fifield wrote:
> > > Responses to pipelined requests are supposed to either have a
> > > Content-Length or use the chunked Transfer-Encoding, both of which
> > > allow you to find the length of the body and the start of the next
> > > response.
> >
> > There are more cases than I summarized here. Section 4.4 of RFC 2616 has
> > all the details of determining message length.
> >
> > David Fifield
> >
> > _______________________________________________
> > Sent through the nmap-dev mailing list
> > http://cgi.insecure.org/mailman/listinfo/nmap-dev
> > Archived at http://SecLists.Org
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org


--
Ron Bowes
http://www.skullsecurity.org/

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org