Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Determine responsibilities for listing available profiles when a redirect is used #603

Closed
rob-metalinkage opened this issue Nov 22, 2018 · 4 comments
Closed

Determine responsibilities for listing available profiles when a redirect is used #603

rob-metalinkage opened this issue Nov 22, 2018 · 4 comments
Assignees
@rob-metalinkage
Labels
due for closing Issue that is going to be closed if there are no objection within 6 days profile-negotiation
Milestone
Conneg 3PWD

Comments

@rob-metalinkage
Copy link
Contributor

If a server redirects the client to another resource using profile negotiation, then the server may know the profile but the existing resource may not.
This is compounded when a resource conforms to multiple profiles, which for part of a hierarchy. Generally speaking it will be hard for static resources to list multiple profiles, whereas the redirecting service must know this information.
@nicholascar
Copy link
Contributor

@rob-metalinkage do you have any suggestions here or is this completely an open question?

@nicholascar nicholascar added this to the Conneg 3PWD milestone May 9, 2019
@nicholascar
Copy link
Contributor

Other than HTTP cookies, there's nothing in the protocol specification about forwarding headers. The client needs to implement this functionality.

@nicholascar nicholascar mentioned this issue Aug 8, 2019
Closed
@rob-metalinkage rob-metalinkage mentioned this issue Aug 12, 2019
Closed
@rob-metalinkage
Copy link
Contributor Author

Note that the underlying issue is now #1040 - once that is addressed examples need to be checked and updated and sequence diagrams added.

@rob-metalinkage rob-metalinkage mentioned this issue Aug 15, 2019
Closed
@nicholascar nicholascar added the due for closing Issue that is going to be closed if there are no objection within 6 days label Aug 15, 2019
@nicholascar
Copy link
Contributor

Addressed in PR 1037

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rob-metalinkage rob-metalinkage

Labels
due for closing Issue that is going to be closed if there are no objection within 6 days profile-negotiation
Projects
None yet
Milestone
Conneg 3PWD
Development

No branches or pull requests
2 participants
@nicholascar @rob-metalinkage