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.

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

Viewing contents of Default Admin Set on admin dashboard raises exception #808

Closed
1 task done
bess opened this issue Dec 20, 2017 · 3 comments
Closed
1 task done
Assignees

Comments

@bess
Copy link
Contributor

bess commented Dec 20, 2017

If you go to http://qa-epigaea.curationexperts.com/admin/admin_sets/admin_set%2Fdefault you will get an exception. The error is Ldp::BadRequest and it seems to be related to data in the fedora on qa -- the same code works fine in a local development environment.

  • Document the apache configuration that fixes the issue

Backtrace

View full backtrace and more info at honeybadger.io

@bess bess added the bug label Dec 20, 2017
@bess bess changed the title [epigaea/production] Ldp::BadRequest: Viewing contents of Default Admin Set on admin dashboard raises exception Dec 20, 2017
@bess bess added the ready label Dec 20, 2017
@bess bess added in progress and removed ready labels Dec 28, 2017
@bess bess self-assigned this Dec 28, 2017
@bess
Copy link
Contributor Author

bess commented Dec 28, 2017

This is a bug upstream in Hyrax. Ticket opened here: samvera/hyrax#2446

@bess
Copy link
Contributor Author

bess commented Jan 3, 2018

Fixed!

Solution found in samvera-labs/nurax-pre2023#32

  • Test this and see if it fixes the issue
  • if it does, document it, for this project and future work

Connected to:

@bess bess closed this as completed Jan 3, 2018
@bess bess removed the in progress label Jan 3, 2018
@mark-dce
Copy link
Contributor

mark-dce commented Jan 3, 2018

@mkorcy - @bess found a fix for this problem - it's actually a web-server routing issue. If you're using Apache, the solution is as follows:

The fix is to add this line to conf-enabled/passenger.conf:

  PassengerAllowEncodedSlashes on

For more details, check out curationexperts/ansible-samvera#22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants