0
Started

Caching problem `nocache`

Kenneth 4 years ago updated by Christian Fritz 2 years ago 1

I have a cashing problem of some sort. If I use the following bib file then it renders like described in this (http://bibbase.userecho.com/topics/148-parser-issue-if-the-key-contain-ampersand/) previous issue:

http://bibbase.org/show?bib=blog.lausdahl.com/wp-content/uploads/publications/lausdahl.bib&proxy=1&groupby=year

```

undefined (9)

. In .
bibtex 1 download
. In .
bibtex 1 download
. .
bibtex 1 download
. In .
bibtex 1 download
. In .
bibtex 1 download
. In .
bibtex 1 download
. In .
bibtex 1 download
. .
bibtex 1 download
. In .
bibtex 1 download
```

but if I add either `&nocache=1` or `&nocache=0` then it renders correctly. Any idea why this is happening. I assume that `&nocache=1` should be avoided since you probably try to reduce processing by caching the data.

Started

Hi Kenneth,


Thank you so much for reporting this. It allowed me to discover a bug in our caching logic! When using nocache the cache was bypassed but a new cache entry was created (rather then the old one updated). So probably at one point there was a broken bib file and the page was loaded with nocache, and every since the cache was referring to that.


I've cleared the cache and the page is fine again now. We'll also get that bug fixed right away.


Thanks again!