Bug 806371 - [REST API] links are a special construct, neither relative nor absolute
Summary: [REST API] links are a special construct, neither relative nor absolute
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Lili Nader
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-23 15:06 UTC by Andre Dietisheim
Modified: 2015-05-15 01:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:33:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andre Dietisheim 2012-03-23 15:06:02 UTC
If you GET a resource you'd get links to possible operations. those links use hrefs that are neither absolute nor relative. They're a value a client would have to add to the broker base url. In our sense this is not ideal since it requires the client library to know about a service base url:

<link>
    <href>/domains/1329997507457</href>
    <method>DELETE</method>
</link>

We'd strongly prefer absolute URL's since the logic behind resource URLs is then completely opaque for clients. They would not need any special knowledge about a base url, context or whatever.

Comment 1 Mrunal Patel 2012-03-26 22:44:29 UTC
Lowering priority since this could be addressed in a US.

Comment 2 Lili Nader 2012-04-09 20:10:15 UTC
changed all links to absolute

Comment 3 Xiaoli Tian 2012-04-12 10:37:37 UTC
(In reply to comment #2)
> changed all links to absolute

Tested it on devenv-stage-166, all links are absolute like following :
 <href>https://ec2-23-20-212-221.compute-1.amazonaws.com/broker/rest/domains/domx91/applications/scalephp1/cartridges</href>


Note You need to log in before you can comment on or make changes to this bug.