Skip to content
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

Bug on IPv6 numeric addresses treatment #1

Open
cralli opened this issue Jun 12, 2014 · 0 comments
Open

Bug on IPv6 numeric addresses treatment #1

cralli opened this issue Jun 12, 2014 · 0 comments

Comments

@cralli
Copy link

cralli commented Jun 12, 2014

When configuring the Keyrock PEP-proxy to listen to outbound v6 queries and forward them over v6 too towards a backend component this way:

  • Server.js file: app.listen(80, "::");
  • Config.js file: config.app_host = '::1’;

The PEP-proxy correctly attends the query over v6. However, when forwarding (again over v6) to the component, the service URL is not correctly provided (looks like ":" characters are misleading for that parsing process).

Traces for a ContextBroker GE as a backend component are:

400
Bad Request

service '/::1/version' not found

The problem does not happen if we configure the IPv6 component endpoint with a valid FQDN. For instance, the following one works fine in a host where /etc/hosts has the line "localhost6 ::1":

  • Server.js file: app.listen(80, "::");
  • Config.js file: config.app_host = 'localhost6’;

Thanks for your support!

aalonsog pushed a commit that referenced this issue Jan 29, 2019
Merging latest changes from ging/fiware-pep-proxy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant