Andrew Hankinson
Andrew Hankinson
I suspect it's related to #1
http://serpy.readthedocs.io/en/latest/#nested-example
> When using load balancing methods other than the default round-robin method, it is necessary to activate them before the keepalive directive. http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive I don't know if this is actually...
Interesting. Using supervisord I can spawn a number of IIP processes all listening on port 9000; I'm assuming supervisor has an internal routing process. I'm assuming that's why it works...
`MAX_CVT` is what you want; it will be IIIF-compliant, since it advertises the max requestable image in the info.json. (This was a bug that was fixed last year, so it...
I would be cautious about setting MAX_CVT too low... I don't think you will actually save *that* much bandwidth over a slightly higher value, and instances where larger single-image sizes...
Sure! https://universalviewer.io It's hard to link to the grid view directly, but if you go here: https://iiif.bodleian.ox.ac.uk/iiif/viewer/03800c8f-a492-4efd-b13a-7a20c8c24b34 and then click on the four squares in the upper-right corner, then you'll...
You're missing quite a few fields in the info.json response: https://zenodo.org/api/iiif/v2/6d2dbb72-5736-4679-b350-77492092068b:ad623be0-59e3-4468-8927-398573d033c7:BR0000012078165.jpg/info.json Compare with: https://iiif.rism.digital/image/lausanne/Gc_prg/CH_Gc_prg_14/pyr_CH_Gc_prg_14-0993.tif/info.json Different clients look at different data in the info response, so just because one client can...
The `info.json` is created and served by IIP; I'm not sure what your specific setup is, but I'm surprised that it's not just passing that request along to IIP. It's...
Any news on this enhancement?