Nmap Development mailing list archives

nmap http service probe failed for HTTP 1.1


From: Enrico Milanese <enricomilanese () gmail com>
Date: Thu, 3 Dec 2015 16:39:36 +0100

Hello,

I experienced some issues during service identification on an HTTP server.
The remote service negotiates *only*  HTTP 1.1 connections.
The remote service discarded (connection close) all the HTTP 1.0 negotiations.

At this time the nmap-service-probes has only TCP probes with HTTP 1.0

"""
Probe TCP GetRequest q|GET / HTTP/1.0\r\n\r\n|
Probe TCP HTTPOptions q|OPTIONS / HTTP/1.0\r\n\r\n|
Probe TCP FourOhFourRequest q|GET /nice%20ports%2C/Tri%6Eity.txt%2ebak
HTTP/1.0\r\n\r\n|
"""

Is it possible to define another TCP probe for this scenario using
HTTP 1.1 negotiation?

Ex:
Probe TCP GetRequest q|GET / HTTP/1.1\r\nHost: www.example.com\r\n\r\n|

Do you see any drawbacks?

Regards

-- 
Enrico Milanese

E-mail: enrico.milanese (at) gmail.com
$ gpg --keyserver pgp.mit.edu --recv-key 0x20112445
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


Current thread: