-
Notifications
You must be signed in to change notification settings - Fork 276
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
When deploying in non-ROOT context in Archival mode, ServerRelativeArchivalRedirect does not resolve URLs correctly #92
Comments
Hi Lauren, I updated the documentation. Maybe this section will be of help to you: https://github.com/iipc/openwayback/wiki/How-to-install#the-access-url-for-the-collection. |
Using the documentation at https://github.com/iipc/openwayback/wiki/How-to-install, I went through several install scenarios with different outcomes.
and to have: - I restarted Tomcat and go to http://localhost:8080/archive/wayback/ as the documentation suggests, but I get a 404 page.I go to http://localhost:8080/archive/ and get the message: archive This is OpenWayback. Any URL in ARC files accessible to this sevice can be searched above.
Attempt 2: Attempt 3: Deployed in ROOT context using CDXCollection.xml, and it worked fine. Attempt 4:
Attempt 5:
From: ulrichhave [notifications@github.com] Hi Lauren, I updated the documentation. Maybe this section will be of help to you: https://github.com/iipc/openwayback/wiki/How-to-install#the-access-url-for-the-collection. — |
I am replacing this issue with #131 that you may or may not find to be more sensible. |
Update cdx server README.md
I am running openwayback in Archival URL Replay Mode. I do not have openwayback deployed in the ROOT context.
I have this bean in my wayback.xml:
The issue seems to be that handleRequestWithCollection in ServerRelativeArchivalRedirect uses the first path segment to parse the collection name out of the referer. Because I am not deploying openwayback in the ROOT context, the collection name is not the first path segment. Instead the code seems to set the context path as the collection name which results in a failure to correctly resolve the URL.
Issue can be seen with: http://webarchive.library.unt.edu/unt/eotcd/20131004144902/http://research.library.unt.edu/eotcd/wiki/Main_Page
In the HTML is:
Trying to resolve those CSS URLs results in an infinite loop.
The text was updated successfully, but these errors were encountered: