Content-Location and Location: Keep Report Identity Separate from Navigation
An integration can receive two URI-bearing headers with different meanings. Keep the identity of returned report content separate from a resource location or navigation decision.

Key takeaway: Content-Location is representation metadata; it does not replace Location or authorise a redirect.
1. Identify which header was returned
RFC 9110 describes Content-Location as an identifier for the resource corresponding to the enclosed representation. Location has separate semantics that depend on the response status. Record the response status, original request target and each header independently before deciding what the client should do next.
Do not implement a generic rule that follows whichever header contains a URL. A returned report and a newly created resource may have related identifiers, yet they are not interchangeable. ProSight Software integration behaviour must be confirmed for the actual deployment rather than inferred from a general HTTP definition.
2. Preserve the returned representation
Save the response content, its media type, acquisition time and relevant permitted metadata. Keep the request context with the stored report so a later investigator can identify what filters or scope produced it. Exclude credentials and sensitive operational data from shared diagnostic examples.
In a hypothetical reporting service, one response contains a summary receipt and an identifier for that receipt. Treating the identifier as the destination for a later update could change a different resource than intended. This example describes a client-design risk, not a promised ProSight Software feature.

3. Keep trust and navigation decisions explicit
Resolve references according to the HTTP library and the actual interface contract. Validate any proposed follow-up destination against the application's approved origin and access policy before a request is made. Never forward authorisation material to an unrelated destination merely because it appeared in a response field.
A URI is not evidence of shared ownership, permission or data freshness. Where different identifiers are supplied, document their roles: request target, created resource, returned representation or retrieval reference. Keep these fields separate in logs and internal models so a display label cannot silently turn one into another.
4. Test the client's next action
Use a controlled fixture with distinguishable targets to confirm which URI the client records and which it actually requests. Include the response status and method in the test evidence. A test that checks only the final screen can miss an unnecessary network request or a wrong target hidden by a successful response.
For acceptance, prove that report provenance is retained and that navigation follows the documented status and header contract. Keep state-changing actions under their own explicit rules. If the service contract leaves the relationship ambiguous, seek clarification before automating a follow-up write.
Practical acceptance checklist
Retain the status, original target and both header names.
Store report identity separately from navigation destinations.
Validate origins before any follow-up request.
Test the actual method and target selected by the client.
Recommended equipment / related solutions
Use the platform overview to frame the monitoring requirement, then discuss an application-specific integration through ProSight Custom. Confirm the supported interface, version, limits and deliverables for the actual deployment; these protocol examples do not promise a feature on every installation.
Practical FAQ
Should every Content-Location trigger a redirect?
No. It is not a substitute for Location or the status-specific navigation rules.
Need help with your application?
Share the application, device or interface documentation, sanitised diagnostic evidence and required outcome so ProSense can assess the next step.



.png)
Comments