-
The demo site is not necessarily a good starting point for a new viewer application.
-
If GitHub Pages starts supporting HTTPS for custom domains, we'll need to fetch everything over HTTPS to avoid mixed-content warnings in the browser. The S3 website endpoint doesn't support HTTPS. The regular endpoint only supports HTTPS with an AWS wildcard cert, and as a result the bucket name can only contain dots if old-style path-based hosting is used. Rename the bucket, switch to HTTPS using the regular endpoint with virtual hosting, and drop complications that were needed for the website endpoint.
-
The total size including overlaps should be a power of 2.
-
Otherwise we're only adding slides.
-
-
Refresh only if the stamp has changed.
-
It was only needed for JSONP.
-
-
The only remaining major browser that doesn't support CORS is IE9, which is only supported on Windows Vista, which will go EOL next April. Close enough.
-
This reverts commit 093fde4.
-
-
-
-
Use OrdinaryCallingFormat to work around failure to validate S3 wildcard cert with bucket names containing dots. Fixes exception: ssl.CertificateError: hostname 'demo.openslide.org.s3.amazonaws.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com' -
-
Internet Explorer < 9 is EOL, so we don't need to stay with jQuery 1.x anymore.
-
-
openslide.org is not itself HTTPS, so this won't make much difference to end-user security, but it's a good general practice.
-