Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Probe a host through a given ip from the input list

クローズ
  • 何か問題がありますか？
#2,667 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 3 日以内に返信

@mazzz3r がすでに取り組んでいます。

2026年10月11日 から。

  • #2668 @mazzz3r による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go
領域
cli, networking

調査の方向性

The issue names -pa, the fastdialer.IP context value, favicon requests, ztls handshakes, and -maxhr, but does not identify source files or tests. Start by tracing how -pa passes IPs into the dialer and how redirects and auxiliary requests use that context; the issue says the implementation is in #2668 and depends on projectdiscovery/fastdialer#580. Done means a given IP is used while hostname-based Host and SNI are preserved, with the listed redirect, IPv6, favicon, ztls, and per-IP error cases handled.

索引モデルが issue の本文から書いたものです。

説明

Type: Enhancement
Please describe your feature request:

An input line that gives the ip to probe a target through, like curl --resolve: the connection goes to the ip, and the hostname stays in the Host header and SNI. The JSON line nuclei would use for the same thing (https://github.com/orgs/projectdiscovery/discussions/7862) fits, so one list could feed both tools:

{"target": "https://app.example.com", "ip": "192.0.2.10"}
{"target": "https://app.example.com", "ip": "192.0.2.11"}
Describe the use case of this feature:

Probing a vhost on a given server, an origin behind a CDN, or one host on each of its servers. The vhost,ip input form builds the URL from the ip and sends the vhost only as the Host header, so there is no SNI, and url and host report the ip. -pa probes the ips DNS returns, not given ones, and the way it passes each ip doesn't reach them correctly. With app.test resolving to 127.0.0.1 and 127.0.0.2, a server on each whose title is its address, and redir.test redirecting to other.test, which resolves to 127.0.0.3 (dev at c9148f0):

$ echo http://app.test:18080 | httpx -pa -title -ip -silent
http://app.test:18080 [srv=127.0.0.2 host=app.test:18080] [127.0.0.1]
http://app.test:18080 [srv=127.0.0.2 host=app.test:18080] [127.0.0.2]

$ echo http://redir.test:18201 | httpx -pa -fr -title -ip -sc -silent
http://redir.test:18201 [302,200] [srv=127.0.0.1 host=other.test:18202] [127.0.0.1]
  • -pa passes each ip in the fastdialer.IP context value, and fastdialer serves the second ip from the dialer cached for the first one (projectdiscovery/fastdialer#579, PR projectdiscovery/fastdialer#580).
  • That value pins every dial made for the request, so a redirect to another host followed with -fr goes to the probed ip.
  • IPv6 ips are passed in brackets, which fastdialer doesn't accept as an ip, so those probes fail with no ips provided in dialWrap.
  • The favicon request and the ztls handshake are made with context.Background(), so they drop the ip and reach the host through DNS, and -maxhr counts errors per host:port, so errors on one ip skip the other ips of the host.

Implemented in #2691, which replaces #2668. The fastdialer change it needs (projectdiscovery/fastdialer#580) is released in v0.6.0, which dev already requires.

主要言語
Go
スター
10.6k
フォーク
1.1k
平均マージ
3日 1時間
マージ済み PR（30日）
17

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

projectdiscovery/httpx のほかの issue

projectdiscovery/httpx の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。