René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`Invoke-WebRequest -PassThru`, when combined with `-OutFile`, should reflect the download file path.","articleBody":"### Summary of the new feature / enhancement\n\nThanks to a contribution by @CarloToso, since v7.4.0 it has been possible to pass a _directory_  rather than a file path to `-OutFile`, in which the web cmdlets use the (ultimate) target URL's _last segment_ as the file name.\r\n\r\nGiven that, when redirections are involved,  you won't know what that last segment is, being able to _programmatically_ discover the resulting full download file path is important.\r\n\r\nThis will also apply to the planned support for using a  _server-suggested_ output file name via a `Content-Disposition` response header field - see PR https://github.com/PowerShell/PowerShell/pull/19385\r\n\r\n(Using `-Verbose` is a way to discover the file name _interactively_; while it's technically possible to programmatically parse the verbose output, that would be both cumbersome and brittle).\r\n\r\nThus - at least when `-OutFile` is used - the `[Microsoft.PowerShell.Commands.WebResponseObject]` instance returned via `-PassThru` should have an `.OutFile` property or similar that reflects the output file's full path.\r\n\r\nRelated:\r\n\r\n * #21081\n\n### Proposed technical implementation details (optional)\n\nI don't know whether it's worth extending `[Microsoft.PowerShell.Commands.WebResponseObject]` or not.\r\n\r\nIf not, an ETS `NoteProperty` member could be used.\r\n\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2024-01-16T19:57:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/21082/PowerShell/issues/21082"}