Plan uri returned from create plans cannot be used in more complex environments

Bug #1395834 reported by Dimitry Ushakov on 2014-11-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Solum
Medium
Unassigned

Bug Description

When POSTing /v1/plans, the plan URI returned maps to a [PROTOCOL]://[HOST]:[PORT]/[URI] format. This is problematic when used with a reverse proxy, ip forwarder since Solum uses the host and port it's listening on instead of DNS. The user then cannot use the returned URL since HOST is most likely localhost and PORT is most likely behind a firewall.

Example:
- client makes a POST to https://example.com/v1/plans

- example.com is a load balancer than sends a request to 25.0.0.0:443
- nginx listens on port 443 on that node and forwards the request to solum's port 9777
- plan is created and the URL is set to http://localhost:9777/etc

The user cannot use the above url because:
- s/he doesn't have access to localhost
- s/he doesn't have access to port 9777

Adrian Otto (aotto) wrote :

Possible solution here is to use a relative URI in the redirect instead of a URL.

Changed in solum:
status: New → Confirmed
status: Confirmed → Triaged
milestone: none → 2015.1.1

We need to check if this is an issue with the new 'app' model, and fix it if the issue still exists.

Changed in solum:
importance: Undecided → Medium
tags: added: solum-api

Solum has moved away from plan abstraction, so marking this as 'Won't Fix'.

Changed in solum:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers