-
Notifications
You must be signed in to change notification settings - Fork 49
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.
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
Fix shared search URLs #1844
Fix shared search URLs #1844
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know you are leaving for the day so I plan to correct this @laritakr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Taking this for a spin, after I created a work w a fileset for each tenant. I then made a collection. I was going back to the work's show page to add the work to the collection but ran into this error:
Not sure if it's related to the changes in this PR but I'd like to take some time to look into it and maybe correct it here if so.
@laritakr I pushed up what I think may be the fix to the issue described above. Please review at your convenience.
I approve this PR if you agree with my changes. Otherwise ping me again when this is ready, if you decide to do something different to resolve it. Demo: https://share.getcloudapp.com/X6uQAJBN |
As an update, I pulled over the fix from UTK. I retested it and it's all still working. |
Thanks for following up, @ShanaLMoore The changes you made are what I had in mind. |
Fixes remaining problems with UTK issue 80
Blacklight's search_context.js introduces click-jacking behavior for A-tags that conflict with shared search tenant behavior. This click-jacking behavior uses a relative path in its form submission.
The manifestation of this problem is when you click on an item in the shared search tenant catalog index and get a Faraday error that has the port 99999. That 99999 means that there’s no loaded tenant the various endpoints (see AccountEndpoints module) for Solr and Fedora use the nil handler and our nil endpoint handler is loaded. See the NilSolrEndpoint. This is evident in the work of UTK issue 80, where we coerced an ID (which normally renders as a path) to a URL to the host tenant.
To remedy the link jacking, we have two options:
Changes proposed in this pull request:
@samvera/hyku-code-reviewers