PowerShell / PowerShell/PowerShell
Support `Invoke-WebRequest` over Windows named pipes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 55.5k
- Forks
- 8.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 88
Description
Summary of the new feature / enhancement
Docker on Windows listens on a named pipe for HTTP, and so do some other services. e.g. Node.js IPC servers. It would be nice to support this in Invoke-WebRequest.
P.S. This is also not supported in cURL, so I had to resort to using Node.js from the command line to send requests to such named pipe HTTP servers.
Proposed technical implementation details (optional)
Basically the same as how UnixSocket is implemented, but using NamedPipeClientStream instead.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Invoke-WebRequest's existing UnixSocket handling and compare the proposed approach with NamedPipeClientStream. The work is done when Invoke-WebRequest can send HTTP requests to Windows named-pipe servers, including Docker or Node.js IPC examples; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100