Follow redirects #190
Description
From the Dutch Digital Heritage Network we are promoting the use of IIIF (Image API and Presentation API) and the use of persistent HTTP URIs (PIDs). We also promote the user of the Presentation API Validator.
The validator doesn't "follow redirects" which PIDs like ARK and Handle usually require. So when you try to validate for example https://n2t.net/ark:/67039/000c1508174c4d9981482e4f392068c6/iiif.json you will get the error:
Validation Error: Cannot fetch url. Got "HTTP Error 308: Permanent Redirect"
When the ARK URL is followed there's a valid v3 manifest at https://www.ldmax.nl/datasets/q4350196/iiif.json?subject=https://n2t.net/ark:/67039/000c1508174c4d9981482e4f392068c6
The manifest https://n2t.net/ark:/67039/000c1508174c4d9981482e4f392068c6/iiif.json is shown by Mirador, UV and Theseus, so these clients do follow redirect. Shouldn't the validator follow redirects too?
I can't find anything about this topic in the Presentation API specification, but would assume this is "just" HTTP protocol?