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
  • #117
Closed
Open
Issue created Sep 29, 2011 by Administrator@rootContributor

Broken examples

Created by: jfhbrook

A few of the examples are broken due to changes in the routing table api:

  • [fixed] /examples/http/standalone-proxy.js
  • [fixed] /examples/websocket/latent-websocket-proxy.js
  • [fixed] /examples/websocket/standalone-websocket-proxy.js

Also, the last example from the readme quietly terminates immediately.

[fixed] Many of the examples also have broken require paths, but I should have a fix for those bugs in a few minutes.

Edit: Refer to pull request #118 .

Edit2: While the require-based and api-related issues have been resolved, there are still a few breaking examples for me:

  • Everything in /examples/websocket/ crashes for me with the following output:
    josh@pidgey:~/proxy/examples$ node websocket/websocket-proxy.js 
    29 Sep 14:50:03 - Your node instance does not have root privileges. This means that the flash XML policy file will be served inline instead of on port 843. This will slow down initial connections slightly.
    29 Sep 14:50:03 - socket.io ready - accepting connections

    node.js:134
            throw e; // process.nextTick error, or 'error' event on first tick
            ^
    Error: ECONNREFUSED, Connection refused
        at Socket._onConnect (net.js:595:18)
        at IOWatcher.onWritable [as callback] (net.js:186:12)
  • The last example from the readme still terminates immediately without saying anything first. See: https://gist.github.com/1252041
Assignee
Assign to
Time tracking