You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there only exist method to generate an url consistent of the domain and protocol.
I would be nice, if there were also methods/parameters that would allow for generating url paths.
Implementation either using /word/word or maybe using a new data set called url_path_words, as the urls may use English words even in non English locales.
Maybe include a path depth parameter in the url() function as well to include paths in the output.
(For a start defaults to zero in v10 and may be changed to a random length in v11)
We marked it as "waiting for user interest" for now to gather some feedback from our community:
If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.
We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.
We will start the implementation based on:
the number of votes ( 👍 ) and comments
the relevance for the ecosystem
availability of alternatives and workarounds
and the complexity of the requested feature
We do this because:
There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
Every feature we add to faker has "costs" associated to it:
i think we could use localized fake patterns to make this more realistic for web content, mixing in various patterns, depths, numbers, querystrings etc
Activity
github-actions commentedon Apr 6, 2026
Thank you for your feature proposal.
We marked it as "waiting for user interest" for now to gather some feedback from our community:
We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.
We will start the implementation based on:
We do this because:
View more issues which are waiting for user interest
matthewmayer commentedon Apr 7, 2026
i think we could use localized fake patterns to make this more realistic for web content, mixing in various patterns, depths, numbers, querystrings etc
ST-DDT commentedon Apr 7, 2026
I like the idea, but this would make it hard to implement arbritary depth parameters. Also ?... does not belong to the path.
We could use url_path_words/patterns to store common chains though:
matthewmayer commentedon Apr 8, 2026
yeah that makes sense, you could have a variety of localized pathSegments, and then join together a random number of them with slashes.
also once we have this working, we could extend faker.internet.url to optionally add a path