Links not accurate for nested resource

I'm writing a multi-tenant application where absolutely every request has to have a location ID as part of the URL or as a param. How do I make it so that when I POST to a nested resource, like to /locations/{location ID}/contacts, the item I get back includes a link that looks like /locations/{location ID}/contacts/{contact ID}? Right now the links returned from the API are just /contacts/{contact ID}, but this won't work because IDs aren't guaranteed to be unique across locations.

Is there a way for the nesting of resources to only go one way like this?

首先跟踪 POST 响应如何为嵌套的 /locations/{location ID}/contacts endpoint 构建链接，并将其与返回的 /contacts/{contact ID} 链接进行比较。确定父资源上下文在哪个位置丢失，并定义测试以验证生成的链接中保留了 location ID，同时不更改无关资源的路径。