Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N node-http-proxy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 482
    • Issues 482
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • http ... PARTY!
  • node-http-proxy
  • Merge requests
  • !228

Use pipe for stuff

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/coderarity/feature-pipe into master Apr 11, 2012
  • Overview 6
  • Commits 4
  • Pipelines 0
  • Changes 3

Created by: coderarity

This is just a simplification of the code really - I removed a lot of code that was just pretty much a copy of stream.pipe, and used stream.pipe instead.

I also removed a test that caused a bunch of subsequent tests to fail. The reasoning for this removal was that the test shouldn't pass. In the case that it was testing, it was aborting the connection, which in turn caused the proxy to abort the connection. Since this happened before the target server received any data, the test would hang, waiting for the connection to be made. http.request didn't send the data since it was aborted too early. The only way I can think of fixing this is to abort the request (without this other tests would fail), and then send a 'dummy' request so that the test passes. Since this is obviously the inappropriate behavior, and since I wanted to be able to use the subsequent tests, I removed the test in this pull request.

This leaves one more test that doesn't pass. This isn't any different from the master branch - a test is failing because the connection object has a circular reference, and assert.equal uses JSON.stringify. I'm not sure why the connection object has a circular reference, and if this is because of inaccurate behavior, so I left it alone.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/coderarity/feature-pipe