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
  • #703
Closed
Open
Issue created Sep 23, 2014 by Administrator@rootContributor

toProxy option is broken

Created by: samcday

In the first place it's somewhat poorly documented, so perhaps I'm just doing it wrong.

Say I do this:

  req.url = "http://destination/yay";

  proxy.web(req, res, {
    target: "http://mysquidproxy:3128",
    toProxy: true
  });

I should expect squidproxy:3128 to receive a GET http://destination/yay HTTP/1.1. Instead, it receives a GET http:/destination/yay HTTP/1.1 - note the single slash after protocol. It looks like common.urlJoin is causing the munging here.

Assignee
Assign to
Time tracking