invoke-webrequest: add page

[reinhart1010]

• The page (if new), does not already exist in the repository.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.
• The page description includes a link to documentation or a homepage (if applicable).

Version of the command being documented (if known): 7.2.1

After quite a long hiatus I decided to contribute some more on PowerShell (and soon for Indonesian translations for macOS commands).

We have talked a lot about Invoke-WebRequest and "incompatible aliases" when curl and wget are not installed in Windows. So I decided to create a special alias page for them, with a command to check which program (curl/wget or Invoke-WebRequest) was used to evaluate the curl or wget command, despite I'm afraid they won't pass the linter:

Check whether wget is properly installed by printing its version number. If this command evaluates into an error, PowerShell may have substituted this command with Invoke-WebRequest

[tldr-bot]

Hello! I've noticed something unusual when checking this PR:

• The page windows/curl.md already exists under the common platform.
• The page windows/wget.md already exists under the common platform.

Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.

[sbrl]

Thanks for the new page! I've left some comments below for you to review.

[sbrl]

This will overwrite the existing curl page in the common platform.

[sbrl]

Same here. Let's remove these wget and curl pages from this pull request.

[reinhart1010]

I wrote these two pages for two reasons. First is the fact that in PowerShell for Windows, both commands will be substituted with Invoke-WebRequest with incompatible set of accepted parameters when wget or curl is not visible on %PATH%:

and similarly, executing curl and wget without additional subcommand or parameters will still return the same prompt with Invoke-WebRequest if both aren't installed on %PATH%:

As far as I know there are some edge cases where a command documentation is split between common and OS-specific versions, e.g. common/cd and windows/cd. As long as tldr clients still can show the common or platform-specific versions of the same command I still prefer to keep windows/curl and windows/wget this way to avoid confusion among those PowerShell users.

Ah I forgot that the original documentation should be accessed with tldr {{curl|wget}} --platform common instead of tldr common/{{curl|wget}}.

[sbrl]

Oh I see, thanks for clarifying this. This is a rather confusing situation, isn't it?

• cmd.exe is the main shell for Windows, which if you have curl or wget installed works as on Linux
• PowerShell is also an official shell distributed and enabled by default on Windows, where curl and wget resolve → Invoke-WebRequest
• Someone should complain to Microsoft about this awfully confusing behaviour, since curl, wget, and Invoke-WebRequest all have incompatible arguments

With this in mind, your solution here seems to be the best option. Thanks for explaining - not being a Windows user I didn't understand at first.

[marchersimon]

Not entirely sure about the curl/wgetpage, but the content looks fine.
It's not the most elegant solution, but I think the only option we have.