-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Middleware regression: Port mixup and infinite loop #1987
Closed
Krinkle opened this issue
Mar 12, 2016
· 3 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed
Middleware regression: Port mixup and infinite loop #1987
Krinkle opened this issue
Mar 12, 2016
· 3 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Labels
Comments
Thanks for the report. |
budde377
added a commit
to budde377/karma
that referenced
this issue
Mar 21, 2016
Derive port from proxy-protocol if present. Closes karma-runner#1987
budde377
added a commit
to budde377/karma
that referenced
this issue
Mar 22, 2016
Derive port from proxy-protocol if present. Closes karma-runner#1987
budde377
added a commit
to budde377/karma
that referenced
this issue
Mar 22, 2016
Derive port from proxy-protocol if present. Closes karma-runner#1987
@dignifiedquire are you waiting in something else to release this? |
@zzo the time to prepare everything |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enviroment Details
Gruntfile.js
fileSteps to reproduce the behaviour
When the test page make requests that hit the proxy, as of recent (v1.13.x somewhere) the proxy destination wrongly include the Karma server's port (which is irrelevant to my server).
E.g. instead of making requests to
http://krinkle.dev/w/foo
it ends up requesting/w/foo
fromkrinkle.dev:9876
. This resolving to localhost then causes an infinite loop.Actual behavior
You get the idea :)
The text was updated successfully, but these errors were encountered: