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
  • Issues
  • #547
Closed
Open
Issue created Jan 11, 2014 by Administrator@rootContributor

Final changes before 1.0.0

Created by: indexzero

@yawnt found a few minor things when I was using this extensively:

  • EventEmitter3 will not throw on an unhandled error: but without any default handler it's very confusing to debug when your proxy logic is just plain wrong. We should have a default logger if there are no error handlers. cc/ @3rd-Eden
  • We should have a simple(r) .createProxy() method: which is basically just exposing createRightProxy. A lot of our users don't even bother with httpProxy.createServer, they just use new httpProxy.RoutingProxy(). Forcing them to create a server that they will never use feels very awkward.
  • Remove all (soon to be old) caronte links: The README.md and a few other doc links still have hrefs to the caronte branch
Assignee
Assign to
Time tracking