search

netconf-wg / restconf

9 stars 4 forks source link

Location URI (from Last Call Gen-Art review) #72

Closed abierman closed 7 years ago

abierman commented 8 years ago

In a few places, returned data can include URIs that are intended to be usable by the client to retrieve information from the Restconf server. These places include the element for accessing an event stream, the Location header of POST responses, and the URLs for retrieving schema resources (section 3.7). The problem is that implementing this assumes that the server knows a host identifier (domain name or address) that the client can use to access the server. In general, given the ubiquity of NATs, the server doesn't know this.

It seems to me that the two possible solutions are for the server to be able to return a URI relative reference or for the server to use as the host­part of the URL the value in the Host header of the request (which perforce the server knows the client can use to access the server). Perhaps this is a known problem with a known solution and so the draft doesn't bother to mention it. Then again, perhaps in practice the clients and the server are in region of the network containing no internal NATS, and the problem does not arise.

But it seems to me that this could be a very general problem for implementers and they should be instructed how to deal with it. I suspect that the authors know the intended resolution of this issue, but it would help if the resolution was stated explicitly.

abierman commented 7 years ago

Issue was discussed on mailing list. No interest in changing text