Your comments
Thanks for noting and reporting this. That SVG turned out to be using SVG standard 2.0, but Firefox only supports SVG 1.1. We've replaced the file with a version 1.1 one.
I think you are looking for this option:
folding | 1 or 0 | Fold / Unfold everything. Default: 0 (unfold everything). |
(see https://bibbase.org/help)
Thanks for the link. However, it's not a 504 that BiIbBase is getting from ecbiz219.inmotionhosting.com, it's a 200 with a request to upgrade the connection. BibBase will eventually send a 504 to you indicating that it was unable to finish the request, but the details I'm sharing above are already one diagnostic layer deeper than that.
You could probably check with inmotion whether there is a way to disable HTTP2 for your site. Alternatively, if they support https that might resolve the issue as well. I already tried https://noahsd.com/bootstrap_bibbase_test/nsd.bib, but that doesn't seem to be supported yet by your host.
I've spent some more time looking into this, but have not been able to get this to work. At the networking level BibBase receives the data, but the host doesn't send all of it, but instead seems to be requesting an upgrade of the connection to HTTP2 (which is something bibbase doesn't yet implement -- HTTP2 not very common yet). Here are the headers BibBase is receiving back from your host:
HTTP/1.1 200 OK
Date: Sat, 09 Jun 2018 04:25:12 GMT
Server: Apache
Upgrade: h2,h2c
Connection: Upgrade, Keep-Alive
Last-Modified: Thu, 31 May 2018 03:22:39 GMT
Accept-Ranges: bytes
Content-Length: 31529
Keep-Alive: timeout=3, max=100
I don't think this will work. So if you can, please keep hosting your bib file from another host.
Actually, bibbase already sends a User-Agent header "bibbase", so that's not it. If you can find anything in the documentation of this hosting provider that could be relevant for this, or get help from them regarding this error, please let us know.
Customer support service by UserEcho
Thanks for investigating this further and reopening the issue! I agree. This is a bug that needs to be addressed. We'll try to fix it as soon as possible.