Hi everyone, I recently upgraded a Dspace repository from version 6.3 to version 8.1. The service is up and running now, but I'm running into an issue with bitstream URLs. I work for a university library, and our workflow with Dspace 6.3 was to add an item to Dspace, get a bitstream link directly to the file, and then add that link to our library catalogue. After upgrading to 8.1, I can access files if I navigate to them in Dspace, but the old bitstream URLs don't work.
For example, here's an item <https://www.ulethbridge.ca/lib/ematerials/items/7ccb3289-8f31-402b-9bcb-982d87547192>in our repository. Downloading the PDF from that page works fine, but using this Dspace 6 URL <https://www.ulethbridge.ca/lib/ematerials/bitstream/handle/123456789/2714/IL-art-therapy-and.pdf?sequence=1&isAllowed=y> redirects to localhost:4000. Strangely if I remove the two query parameters in the URL like this <https://www.ulethbridge.ca/lib/ematerials/bitstream/handle/123456789/2714/IL-art-therapy-and.pdf>, it then redirects me to https://www.ulethbridge.ca/bitstreams/6e17c8af-c6b5-4657-8f79-eb96822d9950/download (which is missing the /lib/ematerials portion of the URL). I thought at first that the issues above (especially the localhost:4000 one) were due to an httpd configuration issue, but it still seems to happen even if I comment out the ProxyPass and ProxyPassReverse lines in httpd.conf. Our setup is a bit unusual. The root/base URL for this repository is https://www.ulethbridge.ca/lib/ematerials Our university's central IT department manages the ulethbridge.ca domain, but requests to /lib/ematerials get sent to our Dspace server. For what it's worth, this setup has proven to be quite a pain when trying to configure things and I would not recommend it. I suspect that using a subdomain would have saved me a great deal of stress! I can replace the catalogue links with new URLs if needed, but if anyone has any suggestions for how to make the old ones work, it would be greatly appreciated! Software Versions: OS: Windows Server 2016 Dspace: 8.1 Tomcat: 10.1.39 HTTPD: 2.4.54 Node.js: 22.14.0 OpenJDK: 24 (I'm currently running the Dspace front end using "node main.js", but I'll switch to PM2 once I have the bugs worked out) httpd.conf snippet: <VirtualHost *:443> ServerName www.ulethbridge.ca ProxyPreserveHost On RequestHeader set X-Forwarded-Proto https ... ProxyPass /lib/ematerials http://localhost:4000/lib/ematerials ProxyPassReverse /lib/ematerials http://localhost:4000/lib/ematerials </VirtualHost> server.xml snippet: <Host name="localhost" appBase="C:/dspace/webapps" autoDeploy="true" unpackWARs="true"> <Alias>www.ulethbridge.ca</Alias> <Context docBase="/server" path="/lib/ematerials/server" reloadable="true"/> </Host> local.cfg snippet: dspace.server.url = https://www.ulethbridge.ca/lib/ematerials/server dspace.ui.url = https://www.ulethbridge.ca/lib/ematerials config.yml snippet: ui: ssl: false host: localhost port: 4000 nameSpace: /lib/ematerials rest: ssl: true host: www.ulethbridge.ca port: 443 nameSpace: /lib/ematerials/server If there's any other relevant information that I'm missing, please let me know! Thanks, Bryson -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/a3ec23ed-7115-44f4-9240-c37ea11aa9e9n%40googlegroups.com.
