WIP: Add handling to Invoke-Webrequest command for named pipes

[sharktide]

…Not working)

PR Summary

PR Context

Adds support for http servers set up on named pipes with Invoke-Webrequest for easy use.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed

[sharktide]

@microsoft-github-policy-service agree

[sharktide]

@iSazonov Can you help me fix an error? I was working and I got the basic logic working see the file, so what I do is check for npipe:// scheme, if so then pass it to my own function processNamedPipeRequest and then build a response and pass it to internal override processResponse. However, this line in processResponse fails with object reference not set to an instance of an object on named pipe but not on regular requests:

Stream responseStream = StreamHelper.GetResponseStream(response, _cancelToken.Token);

If you see the file; I added a bunch of null checks but they all succeed yet this line throws an error. Any idea of where this is coming from.

[sharktide]

@SeeminglyScience Could you please help?

[iSazonov]

@sharktide You could run Get-Error cmdlet to get stack trace.

[sharktide]

I’ll try

[sharktide]

I'm really busy right now with other projects. The bot can close the PR and I will open a new one or reopen it when I have finished