Re: [NSE][RFC] Transparent support for HTTP Content-Encoding
nnposter <[email protected]> Tue, 21 May 2019 12:53:56 -0600
| Newsgroups | gmane.comp.security.nmap.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2/23/19 2:10 PM, nnposter wrote: > At present the NSE implementation of HTTP does not provide means to > obtain an HTTP response body processed in accordance with header > Content-Encoding. Scripts are unable to deal with compressed responses, > unless making one-off effort on their own, which none of them currently do. > > I am proposing to modify the http.lua library behavior to return the > response body after it has been already decoded. > > More at https://github.com/nmap/nmap/issues/1493 > Please review the proposal and comment. FYI, the code has been committed in r37627. HTTP responses compressed with gzip are now returned decoded/inflated. See https://github.com/nmap/nmap/pull/1571 for details. Cheers, nnposter _______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/