Bibbase is accessing cached version of bibtex file
I am using Bibbase for the publication page for our lab group, and I am hosting the bibtex file on our university's website server. The issue I am facing with bibbase is even though I update the bibtex file (available here: https://research.seas.ucla.edu/licos/files/2019/08/publicactions_v1.bib), the changes are not reflected on the publications page of our website. It seems that bibbase is still accessing the older version of the file instead of the updated file. I have tried using the option 'nocache=1', but it still does not update the content of the page with the updated bibtex file.
Can you please take a look into this and let me know?
Customer support service by UserEcho
Happy to take a look! Can you send me also the URL of the publication page where this bibtex file is used?
I think I found it. It https://www.licos.ee.ucla.edu/publications/ right?
Can you help me find the change you made to the bibtex file that you don't see updating on the page? The page has 301 publications, and the bibtex files also contains 301 entries, so it's not obvious what the difference is.
Yes, the link is correct, and the number of entries displayed is correct as well.
I have made the following changes:
1. I have added URL and abstract to the following publication which does not appear on the page:
2. I have added an author to the following publication but it does not appear as well:
Please let me know if you need any other information.
This looks like an issue with your hosting provider, which is where the bibtex file is hosted. They seem to use a CDN (content delivery network, essentially a globally distributed cache) and the BibBase server seems to be getting the same result each time it requests your bib file. Yahya Ezzeldin from https://research.seas.ucla.edu/arni/ actually reported the same issue just recently.
> curl -I https://research.seas.ucla.edu/licos/files/2019/08/publicactions_v1.bib
date: Thu, 17 Dec 2020 01:40:32 GMT
cache-control: public, max-age=31536000
x-cache-bypass-reason: Arguments found
If I interpret that max-age for the cache correctly then the problem may solve itself about 9 hours. after your editing. But I'll also look for a way to request bibbase to work around this (there might be ways to force the CDN provider to refetch the latest version).
In case it helps, this is the response the bibbase server is currently receiving back from your host:
with these response headers:
You may want to try a different hosting provider for your bibtex file, or you can let BibBase host your bibtex file directly in case one of our premium plans makes sense for your group(s).
Thank you. I see that the last modified time stamp on the file is of Dec 12 from your message. The changes I made to the bibtex file that I mentioned in this thread earlier are done on Dec 12 (after the mentioned modifications time stamp in the message above), and on Dec 16. But here is another issue that I am still not clear about:
When I download the bib file using the link (https://research.seas.ucla.edu/licos/files/2019/08/publicactions_v1.bib), I am able to see the changes made by me on Dec 12 in the downloaded version of the file (which is change 1 in the mentioned changes to the bibtex file in this thread). Therefore, I assume that the older version is no longer cached by the hosting provider. However, the BibBase page does not show these changes (where it should add the URL and the abstract to the mentioned publication). I am not clear what is the issue here?
For the changes I made on Dec 16 (which is change 2 in the mentioned changes to the bibtex file in this thread), they are still not updated on the downloaded version of the file using the link. Therefore, it seems like my hosting provider is still distributing the older cached version of the file as you suggested.
What I've shown you above is verbatim what the bibbase server receives when requesting your bibtex file. I know it is confusing that you and I when we request that seemingly same URL get a different response, but that's how CDNs work: they actually consist of very many servers distributed around the globe such that users can always get the pages they request as fast as possible, namely by being served by the closest such server. The bibbase server is located in Oregon and may hence be receiving the file from a different server in the CDN of your hosting provider.
Here is a screenshot of me making the exact same request from my machine (in California) and from the bibbase server in Oregon. As you can see the results are different.
So unfortunately there is nothing I can do here until your hosting provider refreshes their CDN cache serving that region in Oregon. I've already tried tricking your provider into refreshing the file by adding extra URL parameters (?something=1). This sometimes works because it's a different URL. But in this case it didn't.
That makes a lot more sense. Thank you very much for helping me with this. I am trying to see if the hosting provider can resolve this issue now otherwise we will look for other options.