Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[WIP] Rails 5 fix - depend on an express-http-proxy version that can handle Transfer-Encoding: chunked & IPv6 #8

Closed
wants to merge 2 commits into from

Conversation

himdel
Copy link
Contributor

@himdel himdel commented Feb 18, 2016

This fixes the Parse error messages (in node console) and the corresponding net::ERR_EMPTY_RESPONSE (in browser).

Also change the proxy from 127.0.0.1:3000 to http://[::1]:3000, and update express-http-proxy to parse that correctly.

Not sure if we want to merge like this, or wait for villadora/express-http-proxy#47 and villadora/express-http-proxy#48.

Also relevant: nodejs/node#5308 - PR nodejs/node#5314

@himdel himdel changed the title Rails 5 fix - depend on an express-http-proxy version that can handle Transfer-Encoding: chunked Rails 5 fix - depend on an express-http-proxy version that can handle Transfer-Encoding: chunked & IPv6 Feb 18, 2016
@himdel himdel changed the title Rails 5 fix - depend on an express-http-proxy version that can handle Transfer-Encoding: chunked & IPv6 [WIP] Rails 5 fix - depend on an express-http-proxy version that can handle Transfer-Encoding: chunked & IPv6 Feb 18, 2016
@himdel
Copy link
Contributor Author

himdel commented Feb 18, 2016

@miq-bot add_label wip

@himdel
Copy link
Contributor Author

himdel commented Feb 18, 2016

WIP because the IPv6 change is not quite finished.. http.request with hostname: '::1' and port: 3000 will try to access ::1:3000 instead of [::1]:3000, which fails.

Puma listens on ::1 by default, not 127.0.0.1.
Also prepending http to be explicit about the protocol.
@miq-bot
Copy link
Member

miq-bot commented Feb 18, 2016

Checked commits https://github.com/himdel/manageiq-ui-self_service/compare/0aee3bf3cba42dded6c586d9c5a04aca5546a8fd~...39fd31c011122761dcba3a546b93192eca39f399 with ruby 2.2.3, rubocop 0.34.2, and haml-lint 0.13.0
0 files checked, 0 offenses detected
Everything looks good. ⭐

@himdel
Copy link
Contributor Author

himdel commented Feb 24, 2016

Closing in favour of #11 - express-http-proxy development is ..less active these days..

@himdel himdel closed this Feb 24, 2016
@himdel himdel deleted the rails5-fix branch February 24, 2016 14:22
@miq-bot miq-bot added the wip label Apr 22, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants