epi052/feroxbuster · error

Unable to parse path from url

Error message

Unable to parse path from url: {}

What it means

After a successful remote-wordlist download, wrapped_main tries to derive a filename via response.url().path_segments(). If the URL has no parseable path segments (path_segments returns None, which happens for URLs whose path cannot be split, e.g. cannot-be-a-base URLs), it bails with this message. The scan cannot proceed without a filename to cache the wordlist under.

Solutions

1. Use a conventional http(s) URL with a real path ending in a filename
2. Download the wordlist locally and pass the file path instead
3. Check redirect behavior (curl -L) to see the final URL's path
4. Strip query/fragment oddities from the URL

Example fix

// before
ferox -u https://t.com --wordlist data:text/plain,word
// after
curl -o words.txt https://example.com/lists/common.txt && ferox -u https://t.com --wordlist words.txt

const u = new URL(wordlistUrl); if (!u.pathname || u.pathname === '/') throw new Error('wordlist URL has no path segments');

function hasPathSegments(u) { try { return new URL(u).pathname.split('/').filter(Boolean).length > 0; } catch { return false; } }

When it happens

Trigger: --wordlist pointing at a URL whose response URL lacks path segments — e.g. a non-hierarchical/cannot-be-a-base URL (data:, mailto:) or a redirect landing on a URL with an empty or unsegmentable path.

Common situations: Redirect chains that land on opaque URLs, misconfigured shorteners, or passing scheme-only/opaque URLs as the wordlist source.

Understand the failure class

Background: "Invalid URL" errors: why new URL(), URI.parse, and reqwest::Url reject your string — missing scheme, whitespace, and bad path format — this error's family across 39 libraries.

• Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.

Related errors

• [ ] Unable to download wordlist from url
• Unable to parse filename from url's path
• Could not get underlying wordlist
• Could not parse
• Did not find any words in

AI-assisted analysis of epi052/feroxbuster@1f595dab5c (2026-09-13). Data as JSON: /api/errors/840f2e3c233b8082. Report an issue: GitHub.

Appendix: source

Thrown at src/main.rs:276

        for source in &config.wordlist {
            if source.starts_with("http") {
                // found a url scheme, attempt to download the wordlist
                let response = config.client.get(source).send().await.context(format!(
                    "Unable to download wordlist from remote url: {source}"
                ))?;

                if !response.status().is_success() {
                    // status code isn't a 200, bail
                    bail!(
                        "[{}] Unable to download wordlist from url: {}",
                        response.status().as_str(),
                        source
                    );
                }

                // attempt to get the filename from the url's path
                let Some(mut path_segments) = response.url().path_segments() else {
                    bail!("Unable to parse path from url: {}", response.url());
                };

                let Some(filename) = path_segments.next_back() else {
                    bail!(
                        "Unable to parse filename from url's path: {}",
                        response.url().path()
                    );
                };

                let filename = filename.to_string();

                // read the body and write it to disk, then read it back as a wordlist
                let body = response.text().await?;
                std::fs::write(&filename, body)?;

                append_words_from_path(&filename, &mut words, &mut seen)?;
            } else {
                match append_words_from_path(source, &mut words, &mut seen) {

View on GitHub (pinned to 1f595dab5c)