Skip to content

Conversation

@missing0x00
Copy link

This issue most commonly affects HTTP -> HTTPS redirects, but not exclusively. This fixes the script when the affected server uses HTTPS.

Otherwise, Nmap attempted to send unencrypted HTTP requests even if the service was identified as HTTPS.

Tested successfully against both HTTP and HTTPS targets.

@nnposter nnposter self-assigned this Oct 29, 2025
@nnposter
Copy link

The patch assumes that the Location header in the HTTP response will be returned by comm.tryssl(). This is not necessarily a safe assumption because the returned chunk of the response is collected with a single non-blocking <socket>:receive().

Please take a look at #3218, which is a major rewrite of the script.

@nmap-bot nmap-bot closed this in 472b586 Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants