Skip to content

Fix encoded IIIF image service IDs - #342

Merged
ewlarson merged 1 commit into
developfrom
feature/issue-294-iiif-image-api
Aug 21, 2026
Merged

Fix encoded IIIF image service IDs#342
ewlarson merged 1 commit into
developfrom
feature/issue-294-iiif-image-api

Conversation

@ewlarson

Copy link
Copy Markdown
Contributor

Summary

  • preserve the requested IIIF Image API service URL when the advertised @id differs only by percent-decoding
  • continue honoring genuinely different canonical service IDs
  • add a regression test for the University of Wisconsin encoded-slash identifier

Root cause

The Wisconsin info.json endpoint uses an encoded slash (%2F), but its @id returns the same identifier with a decoded slash. The viewer trusted the decoded @id, producing tile URLs that returned 404. The encoded tile URLs return 200.

Verification

  • npm test -- --run src/__tests__/geoblacklight/leaflet_viewer_controller.test.js (13 passed)
  • full frontend test suite (957 passed)
  • production frontend build
  • browser verification against 5WA3TYLSGTMK29A: four IIIF tiles loaded with encoded service URLs and nonzero image dimensions

Fixes #294

@ewlarson
ewlarson marked this pull request as ready for review August 21, 2026 15:47
@ewlarson
ewlarson merged commit 1356c13 into develop Aug 21, 2026
12 checks passed
@ewlarson
ewlarson deleted the feature/issue-294-iiif-image-api branch August 21, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IIIF Image API not supported?

1 participant